compare
cargo-release vs release-please
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | cargo-release | release-please |
|---|---|---|
| Language | Rust | TypeScript |
| Licence | Apache-2.0 | Apache-2.0 |
| Stars | 1.6k | 7.8k |
| Latest | v1.1.7 | v17.11.2 |
| Last push | 2026-11-01 | 2026-11-03 |
| Release cadence | about 35 days between releases | about 10 days between releases |
| Active contributors | 3 commit authors on the default branch in the last 90 days | 7 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.
Full replacementrelease-pleaseOpens a release pull request instead of releasing on every merge.
cargo-release
release-please
- v17.11.22026-08-24bump @google-automations/git-file-utils to ^3.2.0 (f082e5c)
- v17.11.12026-07-31deps: upgrade brace-expansion version to 5.0.8 (6159d83)
- v17.11.02026-07-30add PHPLibrarian strategy (#2862) (9aa4fc0)
- v17.10.42026-07-21dynamically replace changelog reference keyword with 'refs' (5b31578)
- v17.10.32026-07-09src/updaters: add google-cloud-pom-parent to specialArtifacts in librarian-yaml (#2841) (6846245)
cargo-release
unsigned The latest release, v1.1.7, carries no signature GitHub could verify.
Loading the security report
release-please
✓ signed The latest release, v17.11.2, carries a signature GitHub verified.
Loading the security report