Repository navigation
CI: publish to npm via Trusted Publishing (OIDC) - #61
Merged
Merged
Conversation
Replaces the npm_token secret with OIDC authentication: - adds the required id-token: write permission - upgrades npm, since trusted publishing needs npm >= 11.5.1 - drops NODE_AUTH_TOKEN; provenance is now attached automatically Co-Authored-By: Claude Opus 5 <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.
The
npm_tokensecret is expired —npm publishfailed withE404 PUT https://registry.npmjs.org/liquid-loadingon both release attempts. Trusted Publishing is now enabled on npmjs.com, so the token is replaced by OIDC.Changes:
permissions: id-token: write— required for GitHub Actions to mint the OIDC tokennpm install -g npm@latest— trusted publishing needs npm >= 11.5.1NODE_AUTH_TOKEN/secrets.npm_token--provenanceflag neededThe workflow file name stays
npm-publish.yml: the trusted publisher on npmjs.com is matched against repository + workflow file name, so renaming it would break publishing.🤖 Generated with Claude Code