ci: automate releases with release-please and npm trusted publishing - #33
Merged
Conversation
On merge to main, release-please maintains a release PR (version bump from conventional commits); merging it tags the release and publishes to npm via OIDC trusted publishing. The committed changelog file is skipped since the GitHub release already carries the notes. A pr-title check keeps squash-merge titles conventional.
simonepri
force-pushed
the
ci/release-automation
branch
from
June 8, 2026 09:38
8566b8d to
39b8f27
Compare
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.
Sets up release-on-merge so we stop publishing by hand (
npis local/interactive).How it works once merged:
NPM_TOKENstored in the repo, and releases get provenance attestations.No committed
CHANGELOG.md—skip-changelogis set, since the GitHub release already carries the notes.Bootstrap is anchored to the v0.6.0 commit, so the first release PR it opens will be 0.6.1 (the already-merged wmic fix).
Requires two one-time settings before publishing works
pidtree→ Settings → Trusted Publisher → GitHub Actions: reposimonepri/pidtree, workflowrelease-please.yml.After merge: release-please opens the 0.6.1 release PR → you merge it → it publishes automatically.