compare
release-please vs semantic-release
The same facts for both, read from GitHub every night, and the relation a person reviewed.
| Fact | release-please | semantic-release |
|---|---|---|
| Language | TypeScript | JavaScript |
| Licence | Apache-2.0 | MIT |
| Stars | 7.6k | 24k |
| Latest | v17.11.2 | v25.0.9 |
| Last push | 2026-10-05 | 2026-10-06 |
| Release cadence | about 10 days between releases | too few releases |
| Active contributors | 6 commit authors on the default branch in the last 90 days | 3 commit authors on the default branch in the last 90 days |
| Flags | none | none |
How they relate
release-please replaces semantic-release. Alternatives to semantic-release →
Full replacementOpens a release pull request instead of releasing on every merge.
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)
semantic-release
- v25.1.0-alpha.12026-10-06integrate @semantic-release/core engine (#4256) (1beed12)pre-release
- v26.0.0-beta.22026-09-25release: trigger (76fa7c6)pre-release
- v26.0.0-beta.12026-08-07ci: update Node.js engine version and test matrix (#4269) (39b1ea6)pre-release
- v25.0.92026-08-05do not expose the authenticated repository URL in EGITNOPERMISSION errors (#4283) (8d905a5)
- v25.0.82026-07-18handle potential null values in commit message and gitTags trimming (0a60004)
release-please
✓ signed The latest release, v17.11.2, carries a signature GitHub verified.
Loading the security report
semantic-release
✓ signed The latest release, v25.0.9, carries a signature GitHub verified.
Loading the security report