Skip to content
Switch branches/tags

cargo release

Build Status Donate

Performs release best-practices, including:

  1. Ensure the git working directory is clean.
  2. Bump the version in Cargo.toml
  3. Create a git tag for this version
  4. Run cargo publish (if not disabled)
  5. Bump version for next development cycle
  6. git push

Features for workspaces include:

  • Report which crates might be able to be skipped
  • Update version ranges in dependent crates
  • Optionally using a single commit for all version bumps


Current release: 0.13.11

cargo install cargo-release


cargo release [level]

  • See the reference for more on level, other CLI arguments, and configuration file format.
  • See also the FAQ for help in figuring out how to adapt cargo-release to your workflow.


  • Your project should be managed by git.

Dry run

We recommend calling cargo release --dry-run -vv with your custom options before actually executing it. The dry-run mode with verbose output will print all commands to execute during the release process. And you will get an overview of what's going on.


Licensed under either of


Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.


I'm now accepting donation on liberapay, if you find my work helpful and want to keep it going.