compare
Changesets vs Commitizen
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Changesets | Commitizen |
|---|---|---|
| Language | TypeScript | Python |
| Licence | MIT | MIT |
| Stars | 12k | 3.5k |
| Latest | @changesets/cli@3.0.3 | v4.19.1 |
| Last push | 2026-10-04 | 2026-10-06 |
| Release cadence | about 1 day between releases | about 15 days between releases |
| Active contributors | 13 commit authors on the default branch in the last 90 days | 9 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 →
Full replacementChangesetsVersions from changeset files written in each pull request instead of commit messages.
PartialCommitizenBumps the version, writes the changelog and tags from conventional commits, but does not publish packages or releases.
Changesets
- @changesets/cli@3.0.32026-09-14Updated dependencies [3f163da, bfe9050, e522996]:
- @changesets/get-release-plan@5.0.22026-09-14Updated dependencies [e522996]:
- @changesets/apply-release-plan@8.1.12026-09-14Updated dependencies [e522996]:
- @changesets/config@4.0.12026-09-14
- @changesets/release-utils@1.0.12026-09-04Updated dependencies []:
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
Changesets
✓ signed The latest release, @changesets/cli@3.0.3, carries a signature GitHub verified.
Loading the security report
Commitizen
unsigned The latest release, v4.19.1, carries no signature GitHub could verify.
Loading the security report