cargo-release review
A Cargo release tool that checks Git state, manages versions, and defaults to dry runs.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
cargo-release is a command-line Cargo subcommand for preparing and carrying out Rust crate releases. It is aimed at maintainers who want release checks and version changes in their Cargo workflow, especially those managing workspaces or dependent crates. Before a release, it can check the branch, remote synchronization, and working-tree cleanliness. It manages crate versions, detects changes that can help identify crates that may not need a release, and publishes through `cargo publish`. Git tags and pushes are also part of its release workflow. The default dry-run mode makes it suited to maintainers who want to review an execution before explicitly running it.
Its scope is focused rather than a general release system: the documented workflow centers on Rust crates, Cargo, Git, and publishing through `cargo publish`. Workspace support can update dependent crates when versions change, which matters for repositories where crate releases are linked. For file updates before release, cargo-release supports search-and-replace, including changelog updates, and a pre-release hook can be customized for steps such as changelog generation. That offers extension points, but changelog generation is hook-based rather than the central release capability. Teams seeking broad language or artifact coverage should look for a tool built for that wider release scope.
The execution model favors deliberate release preparation: checks run before the release, and dry-run is the default until execution is explicitly requested. It requires a Git-managed project, so it is not a fit for repositories without Git. The product is free and open source, with self-hosted use and Linux, macOS, and Windows listed as platforms. Rust maintainers who want version management, workspace handling, publishing, and Git tagging in a cautious CLI workflow are the clearest fit. Teams that need release automation outside Cargo or want changelog generation as a built-in core function should consider alternatives.
cargo-release pros and cons
- Where it wins
- Checks branch, remote sync, and working-tree cleanliness before release
- Handles workspace versions and dependent-crate updates
- Defaults to dry-run mode and supports Git tags and crate publishing
- Where it doesn't
- Requires a Git-managed project
- Focused on Rust crates and Cargo workflows
- Changelog generation depends on a customizable pre-release hook
cargo-release fact sheet, pricing and score →
Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.
Last updated · How we research and update