compare
Commitizen vs release-please
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Commitizen | release-please |
|---|---|---|
| Language | Python | TypeScript |
| Licence | MIT | Apache-2.0 |
| Stars | 3.5k | 7.6k |
| Latest | v4.19.1 | v17.11.2 |
| Last push | 2026-10-06 | 2026-10-05 |
| Release cadence | about 15 days between releases | about 10 days between releases |
| Active contributors | 9 commit authors on the default branch in the last 90 days | 6 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 →
PartialCommitizenBumps the version, writes the changelog and tags from conventional commits, but does not publish packages or releases.
Full replacementrelease-pleaseOpens a release pull request instead of releasing on every merge.
Commitizen
- 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)
- v4.17.12026-08-17init: skip hook question when no installer is present
- v4.17.02026-07-29cmd/version: add support for --next USE_GIT_COMMITS
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)
Commitizen
unsigned The latest release, v4.19.1, 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