compare
Changesets vs release-please
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | Changesets | release-please |
|---|---|---|
| Language | TypeScript | TypeScript |
| Licence | MIT | Apache-2.0 |
| Stars | 12k | 7.6k |
| Latest | @changesets/cli@3.0.3 | v17.11.2 |
| Last push | 2026-10-04 | 2026-10-05 |
| Release cadence | about 1 day between releases | about 10 days between releases |
| Active contributors | 13 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 →
Full replacementChangesetsVersions from changeset files written in each pull request instead of commit messages.
Full replacementrelease-pleaseOpens a release pull request instead of releasing on every merge.
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 []:
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)
Changesets
✓ signed The latest release, @changesets/cli@3.0.3, carries a signature GitHub verified.
Loading the security report
release-please
✓ signed The latest release, v17.11.2, carries a signature GitHub verified.
Loading the security report