Paul Campbell
48a5ed7a3b
All checks were successful
Rust / build (push) Successful in 7m24s
ci/woodpecker/push/cron-docker-builder Pipeline was successful
ci/woodpecker/push/push-next Pipeline was successful
ci/woodpecker/push/tag-created Pipeline was successful
Release Please / Release-plz (push) Successful in 3m22s
ci/woodpecker/cron/cron-docker-builder Pipeline was successful
ci/woodpecker/cron/push-next Pipeline was successful
ci/woodpecker/cron/tag-created Pipeline was successful
18 lines
818 B
Markdown
18 lines
818 B
Markdown
# How to create a new Release
|
|
|
|
## TLDR
|
|
|
|
1. Merge PR `chore: release`
|
|
2. Wait for `push-main` workflow to complete
|
|
3. Replace Release Notes body with details from CHANGELOG (remove crates and duplicates)
|
|
4. Update thread: <https://mitra.kemitix.net/post/01907ef5-5bd9-b0b6-2b8a-e29762541d78>
|
|
|
|
## Detail
|
|
|
|
The workflow in `.forgejo/workflows/push-main.yaml` will create or update a PR whenever `main` branch is updated.
|
|
|
|
The create the new release, merge this PR. It will automatically create the Release on the `git-next` repo, and publish crates to <https://crates/io>.
|
|
|
|
The Release notes that are included with the create Release are currently incorrect, and will need to be manually updated from the `CHANGELOG.md`. Remove crate headers and any resulting duplicates.
|
|
|
|
Post an update to the Fediverse. See link above.
|