compare
cargo-release vs Commitizen
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | cargo-release | Commitizen |
|---|---|---|
| Language | Rust | Python |
| Licence | Apache-2.0 | MIT |
| Stars | 1.6k | 3.5k |
| Latest | v1.1.7 | v4.19.3 |
| Last push | 2026-11-01 | 2026-10-25 |
| Release cadence | about 35 days between releases | about 14 days between releases |
| Active contributors | 3 commit authors on the default branch in the last 90 days | 11 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
Both replace semantic-release. Alternatives to semantic-release →
Partialcargo-releaseBumps the version, tags and publishes Cargo workspaces from a command, without deriving the bump from commit messages.
PartialCommitizenBumps the version, writes the changelog and tags from conventional commits, but does not publish packages or releases.
cargo-release
Commitizen
- v4.19.32026-10-24scm-provider: prefer full version over floating tags
- v4.19.22026-10-07tags: give ignored tag formats precedence over version formats
- v4.19.12026-10-03bump: use VersionIncrement ordering for bump detection (#2097)
- v4.19.02026-09-22add extensible commit filters
- v4.18.02026-08-19commit: add a tag(--body-length-limit) and a function for command commit (#1849)
cargo-release
unsigned The latest release, v1.1.7, carries no signature GitHub could verify.
Loading the security report
Commitizen
unsigned The latest release, v4.19.3, carries no signature GitHub could verify.
Loading the security report