Repository navigation
ci: automate npm publish on GitHub Release (OIDC + provenance) - #11
Merged
Merged
Conversation
Automate releases without a long-lived NPM_TOKEN: when a GitHub Release (tag vX.Y.Z) is published, the workflow verifies the tag matches package.json, runs lint + the full test suite, and publishes with provenance using npm Trusted Publishing (OIDC). - .github/workflows/release.yml — release-triggered publish job. - docs/RELEASING.md — one-time npm trusted-publisher setup and the bump-via-PR → GitHub Release flow (master is protected). - README points at RELEASING.md. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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.
Automates publishing so releases are intentional and tokenless.
Trigger: a published GitHub Release (tag
vX.Y.Z).What it does: verifies the tag matches
package.json, runslint+ fulltest, thennpm publish --provenance --access public.Auth: npm Trusted Publishing (OIDC) — no
NPM_TOKENsecret. Requires a one-time trusted-publisher config on npmjs (documented indocs/RELEASING.md).Why a Release rather than "publish on every merge to master": merges happen for docs/refactors too, and publishing on each would fail whenever the version wasn't bumped. Tying publishes to a Release keeps versions deliberate.
Includes
docs/RELEASING.md(one-time setup + the bump-via-PR → Release flow, since master is now protected) and a README pointer.🤖 Generated with Claude Code