ci: add release-please, npm trusted publishing#31
Merged
Conversation
ungoldman
force-pushed
the
release-automation
branch
2 times, most recently
from
June 13, 2026 21:50
a7a5e3b to
5e25d51
Compare
accidentally bumped early to 4.0.0 during rewrite
ungoldman
force-pushed
the
release-automation
branch
from
June 13, 2026 22:04
5e25d51 to
f6874de
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
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.
Adds planned release automation:
release-pleasefor versioning and changelog, and tokenless npm publish via OIDC trusted publishing.How it works
On every push to
main, release-please reads the conventional commits since the last release and maintains a release PR that bumpspackage.jsonand prepends toCHANGELOG.md. Merging that PR tags the version and creates a GitHub Release, which triggers the publish job:npm ci, build, thennpm publishauthenticated by a short-lived OIDC token. Provenance attestations are generated automatically.Files added:
release-please-config.json:release-type: node, withinclude-component-in-tag: falseso tags stayvX.Y.Z(matchingv3.0.2)..release-please-manifest.json: seeded to3.0.2, the last published version, so release-please diffs from thev3.0.2tag..github/workflows/release.yml: the release-please job plus the OIDC publish job.Setup needed before this can publish (only you can do these)
ungoldman, repoformat-duration, workflowrelease.yml, and selectnpm publishas the allowed action.What happens on merge
release-please sees the
refactor!breaking commit sincev3.0.2and opens a release PR for 4.0.0 with a generated changelog (the breaking-changes section comes from the commit footer, and the ci/chore/docs commits stay hidden). Review and merge that PR to cut and publish 4.0.0. If the trusted publisher is not configured yet, only the publish job fails, so configure it and re-run that job.Note on CI
This workflow triggers on push to
main, not on PRs, so it does not run on this PR. Thetestsworkflow still runs here. release-please activates once this is merged.