release-plz review
A Rust-focused release tool that handles versioning, changelogs, tags, and publishing.
Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026
For Rust developers maintaining individual crates or Cargo workspaces, release-plz automates the path from Git history to published packages. It analyzes Conventional Commits and checks for API-breaking changes to determine version updates. It can generate or update changelogs with git-cliff, open release pull requests from CI, create Git tags, and publish packages to Cargo registries. The command-line tool can also run locally to update manifests and changelogs, giving maintainers a choice between local use and CI-driven releases.
Its ecosystem fit is a defining strength: release-plz supports GitHub, Gitea, and GitLab, alongside Cargo registries including crates.io. It can update dependencies with cargo update before releasing, and its listed integrations include cargo-semver-checks. This makes it relevant to Rust projects that need releases across more than one Git host, rather than only a GitHub-centered flow. The tool is open source and supports Linux, macOS, and Windows, as well as self-hosted deployment.
The scope is deliberately Rust-oriented: release-plz handles Cargo packages, not a broad range of languages or artifact types. Teams also need to account for the CI setup if they want it to open release pull requests; the official quickstart documents a GitHub Actions workflow. Its support channel is documentation. Choose release-plz if Cargo versioning, changelogs, Git-host releases, and registry publishing belong in one workflow. Teams seeking general-purpose release automation beyond Rust packages should look elsewhere.
release-plz pros and cons
- Where it wins
- Derives version bumps from Conventional Commits and API-breaking-change checks
- Supports Cargo workspaces and changelog generation with git-cliff
- Creates releases on GitHub, Gitea, or GitLab and publishes to Cargo registries
- Where it doesn't
- Focused on Rust packages rather than general-purpose release workflows
- Release pull requests are opened from CI, so teams need a CI workflow for that step
- Support channels listed are documentation
release-plz 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