ci: migrate from semantic-release to release-please#10
Merged
Conversation
Replace semantic-release with release-please for automated versioning and npm publishing. release-please maintains a Release PR; merging it publishes to npm and creates the GitHub release using the built-in GITHUB_TOKEN (no PAT). - Add release-please-config.json + .release-please-manifest.json (seeded 1.3.0) - Rewrite release workflow; add PR-title linting for squash-merge reliability - Remove .releaserc.json and all @semantic-release/* devDependencies - Update CONTRIBUTING/CLAUDE/README docs
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Replaces semantic-release with release-please for automated versioning and npm publishing, and cleans up the old machinery.
Why
semantic-release silently released nothing on
refactor/docscommits, and — due to a customreleaseRulesgotcha — downgraded afeat!breaking change to a minor (1.3.0instead of2.0.0). release-please shows the pending version in a standing Release PR and handlesfeat!/BREAKING CHANGE→ major correctly.How it works now
main→ release-please opens/updates a Release PR (bumpspackage.json, updatesCHANGELOG.md, shows pending notes).GITHUB_TOKEN(no PAT) +NPM_TOKEN.Changes
release-please-config.json(release-type: node) +.release-please-manifest.json(seeded to current1.3.0).github/workflows/release.yml→ release-please + npm publish onrelease_created.github/workflows/pr-title.yml→ lints PR titles as Conventional Commits (PRs are squash-merged, so the title drives the release).releaserc.jsonand all 7@semantic-release/*+conventional-changelog-conventionalcommitsdevDependenciesRequired repo setting
Enable Settings → Actions → General → Allow GitHub Actions to create and approve pull requests so release-please can open its Release PR.
Cleanup
The
RELEASE_TOKENsecret is now fully unused and can be deleted.