chore: migrate release pipeline to release-please#194
Merged
Conversation
Switches releases from per-merge auto-publish (semantic-release) to an accumulating, PR-gated model (release-please): merges land on master, a single Release PR maintains the next version + CHANGELOG, and merging it cuts the tag and triggers publish. - add release-please-config.json + .release-please-manifest.json: lockstep monorepo (root '.' drives one version/tag/CHANGELOG; extra-files bump all 11 published packages to the same version) - add .github/workflows/release-please.yml: maintains the Release PR (via the bot App token so it triggers CI) and, on release, publishes with the same 'yarn workspaces foreach npm publish' step used before (handles workspace:* ) - add root package.json version (source of truth for release-please) - remove semantic-release: release.yml workflow + .releaserc.json - allow 'revert' and 'ci' PR-title prefixes (release-please understands them) Note: keeps the existing yarn-based publish/auth as-is. npm trusted publishing + provenance is a deliberate follow-up (needs per-package npm config and a yarn pack step for workspace:* ).
The npm trusted publisher (OIDC) is configured against the workflow file .github/workflows/release.yml. Keep the release-please + publish workflow under that filename so the OIDC exchange keeps matching; the publish job stays the entry workflow's job, so its OIDC subject is release.yml.
GiovaniGuizzo
left a comment
GiovaniGuizzo
left a comment
Contributor
There was a problem hiding this comment.
Will this bot update the package.json files versions too, or is it going to be manual from now on?
Contributor
Author
|
it should update the package.json as well. |
GiovaniGuizzo
approved these changes
Jun 23, 2026
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
2 participants
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.
updating pipeline to create a release branch using release-please.
the idea is prevent multiples releases by merging to master, but keep a alive PR for the release sharing all the additions made to the release.
by merging the release PR it should release on npm.