Skip to content

Commit

Permalink
chore(releasing): Minor tweaks to patch template (#21227)
Browse files Browse the repository at this point in the history
- The changelog key is added automatically
- The version number should be bumped before running the release cue generation
  • Loading branch information
jszwedko authored Sep 25, 2024
1 parent daa02bb commit 112f13c
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions .github/ISSUE_TEMPLATE/patch-release.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,15 +11,14 @@ Before the release:
- `git fetch && git checkout v0.<current minor version> && git checkout -b prepare-v0.<new version number>`
- [ ] Cherry-pick in all commits to be released from the associated release milestone
- If any merge conflicts occur, attempt to solve them and if needed enlist the aid of those familiar with the conflicting commits.
- [ ] Bump the release number in the `Cargo.toml` to the current version number
- [ ] Run `cargo vdev build release-cue` to generate a new cue file for the release
- [ ] Add `changelog` key to generated cue file
- [ ] Add description key to the generated cue file with a description of the release (see
previous releases for examples).
- [ ] Update version number in `distribution/install.sh`
- [ ] Add new version to `website/cue/reference/versions.cue`
- [ ] Create new release md file by copying an existing one in `./website/content/en/releases/` and
updating version number
- [ ] Bump the release number in the `Cargo.toml` to the current version number
- [ ] Run `cargo check` to regenerate `Cargo.lock` file
- [ ] Commit these changes
- [ ] Open PR against the release branch (`v0.<new version number>`) for review
Expand Down

0 comments on commit 112f13c

Please sign in to comment.