compare
Changesets vs release-it
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Changesets | release-it |
|---|---|---|
| Language | TypeScript | JavaScript |
| Licence | MIT | MIT |
| Stars | 12k | 9.1k |
| Latest | @changesets/cli@3.0.3 | 21.1.0 |
| Last push | 2026-10-04 | 2026-09-17 |
| Release cadence | about 1 day between releases | about 7 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.
Partialrelease-itBumps, tags and publishes to npm and GitHub, interactively or in CI; versions from commits need a plugin.
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 []:
Changesets
✓ signed The latest release, @changesets/cli@3.0.3, carries a signature GitHub verified.
Loading the security report
release-it
unsigned The latest release, 21.1.0, carries no signature GitHub could verify.
Loading the security report