11Release Checklist
22-----------------
3+ * Ensure local ` master ` is up to date with respect to ` origin/master ` .
34* Run ` cargo update ` and review dependency updates. Commit updated
45 ` Cargo.lock ` .
56* Run ` cargo outdated ` and review semver incompatible updates. Unless there is
6- a strong motivation otherwise, review and update every dependency.
7+ a strong motivation otherwise, review and update every dependency. Also
8+ run ` --aggressive ` , but don't update to crates that are still in beta.
79* Review changes for every crate in ` crates ` since the last ripgrep release.
810 If the set of changes is non-empty, issue a new release for that crate. Check
911 crates in the following order. After updating a crate, ensure minimal
@@ -24,6 +26,11 @@ Release Checklist
2426 ` cargo update -p ripgrep ` so that the ` Cargo.lock ` is updated. Commit the
2527 changes and create a new signed tag. Alternatively, use
2628 ` cargo-up --no-push --no-release Cargo.toml {VERSION} ` to automate this.
29+ * Push changes to GitHub, NOT including the tag. (But do not publish new
30+ version of ripgrep to crates.io yet.)
31+ * Once CI for ` master ` finishes successfully, push the version tag. (Trying to
32+ do this in one step seems to result in GitHub Actions not seeing the tag
33+ push and thus not running the release workflow.)
2734* Wait for CI to finish creating the release. If the release build fails, then
2835 delete the tag from GitHub, make fixes, re-tag, delete the release and push.
2936* Copy the relevant section of the CHANGELOG to the tagged release notes.
0 commit comments