This checklist is meant to be used as a guide for the crates.io release process.
Releases are always made in lockstep, meaning that all crates in the repository are released with the same version number, regardless of whether they have changed or not.
- cargo-release:
cargo install cargo-release - git-cliff (patched with orhun/git-cliff#711):
cargo install --git https://github.com/DaniPopes/git-cliff.git --branch fix-include-paths git-cliff
- Make sure you're on the
mainbranch. - (optional) Dry run
cargo-release:cargo release <version> - Run
cargo-release:PUBLISH_GRACE_SLEEP=10 cargo release --execute [--no-verify] <version>- Ignore these warnings:
warning: updating <crate> to <version> despite no changes made since...git-cliffwarningthere is already a tag (<tag>) for ...
- If a failure happened:
- You should have an unpushed commit. After the issue is fixed, retry the release process with
--no-pushand squash the commits together. - If some crates were published before the error, AFAICT you must manually
--exclude <crate>each already-published crate. - Verify that the commit is correct, and push to the repository with
git push --tags.
- You should have an unpushed commit. After the issue is fixed, retry the release process with
- Ignore these warnings:
- Create a new GitHub release with the automatically generated changelog and with the name set to
<repo> v<X.Y.Z>