From 365384a5c11760675768622b8c6e03e1e34ec81f Mon Sep 17 00:00:00 2001 From: Andrew Gallant Date: Wed, 15 Oct 2025 22:54:51 -0400 Subject: [PATCH] doc: move CHANGELOG update before dependency updates It seems better to write this first. Especially so it gets included into crate publishes. --- RELEASE-CHECKLIST.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE-CHECKLIST.md b/RELEASE-CHECKLIST.md index c168574..eb91916 100644 --- a/RELEASE-CHECKLIST.md +++ b/RELEASE-CHECKLIST.md @@ -7,6 +7,7 @@ a strong motivation otherwise, review and update every dependency. Also run `--aggressive`, but don't update to crates that are still in beta. * Update date in `crates/core/flags/doc/template.rg.1`. +* Update the CHANGELOG as appropriate. * Review changes for every crate in `crates` since the last ripgrep release. If the set of changes is non-empty, issue a new release for that crate. Check crates in the following order. After updating a crate, ensure minimal @@ -22,7 +23,6 @@ * crates/printer * crates/grep (bump minimal versions as necessary) * crates/core (do **not** bump version, but update dependencies as needed) -* Update the CHANGELOG as appropriate. * Edit the `Cargo.toml` to set the new ripgrep version. Run `cargo update -p ripgrep` so that the `Cargo.lock` is updated. Commit the changes and create a new signed tag. Alternatively, use