compare
cargo-release vs conventional-changelog
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | cargo-release | conventional-changelog |
|---|---|---|
| Language | Rust | TypeScript |
| Licence | Apache-2.0 | ISC |
| Stars | 1.6k | 8.5k |
| Latest | v1.1.7 | template-v1.4.1 |
| Last push | 2026-11-01 | 2026-11-12 |
| Release cadence | about 35 days between releases | about 1 day between releases |
| Active contributors | 3 commit authors on the default branch in the last 90 days | 4 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.
Partialconventional-changelogChangelog generation from Conventional Commits only, with no version bump or publish.
cargo-release
conventional-changelog
- template-v1.4.12026-11-01@conventional-changelog/template: v1.4.1
- conventional-recommended-bump-v12.1.12026-11-01conventional-recommended-bump: v12.1.1
- conventional-commits-parser-v7.1.42026-11-01conventional-commits-parser: v7.1.4
- git-client-v3.2.02026-10-05@conventional-changelog/git-client: v3.2.0
- conventional-commits-parser-v7.1.32026-10-05conventional-commits-parser: v7.1.3
cargo-release
unsigned The latest release, v1.1.7, carries no signature GitHub could verify.
Loading the security report
conventional-changelog
✓ signed The latest release, template-v1.4.1, carries a signature GitHub verified.
Loading the security report