rust/ripgrep
1
0
Fork 0
mirror of https://github.com/BurntSushi/ripgrep.git synced 2025-05-13 21:26:27 +02:00
Code Issues Releases Activity

release: add note about pushing changes

Browse Source
This commit is contained in:
Andrew Gallant 2021-06-12 08:13:11 -04:00
parent af6b6c543b
commit c44d263419
No known key found for this signature in database
GPG Key ID: B2E3A4923F8B0D44
1 changed files with 2 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
RELEASE-CHECKLIST.md
View File

@ -26,6 +26,8 @@ Release Checklist
`cargo update -p ripgrep` so that the `Cargo.lock` is updated. Commit the `cargo update -p ripgrep` so that the `Cargo.lock` is updated. Commit the
changes and create a new signed tag. Alternatively, use changes and create a new signed tag. Alternatively, use
`cargo-up --no-push --no-release Cargo.toml {VERSION}` to automate this. `cargo-up --no-push --no-release Cargo.toml {VERSION}` to automate this.
* Push changes to GitHub, including the tag. (But do not publish new version of
ripgrep to crates.io yet.)
* Wait for CI to finish creating the release. If the release build fails, then * Wait for CI to finish creating the release. If the release build fails, then
delete the tag from GitHub, make fixes, re-tag, delete the release and push. delete the tag from GitHub, make fixes, re-tag, delete the release and push.
* Copy the relevant section of the CHANGELOG to the tagged release notes. * Copy the relevant section of the CHANGELOG to the tagged release notes.