Repository navigation
ci: publish to npm with trusted publishing (OIDC) - #178
Merged
Merged
Conversation
Drop NPM_TOKEN and registry-url, grant id-token: write to the publish job. Node 24.4.1 pin bumped to 24 (bundled npm 11.4.2 predates OIDC support). Co-Authored-By: Claude Opus 5.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.
Switch npm publishing from the
NPM_TOKENsecret to npm trusted publishing (OIDC).publishjob getspermissions: { contents: write, id-token: write }(contents for lerna tags/releases, id-token for the npm OIDC exchange)registry-urlandNODE_AUTH_TOKENremoved; nothing reads the token anymoreTrusted publisher on npmjs.com:
chyzwar/common, workflowpublish.yaml, no environment. After merge theNPM_TOKENrepo secret is deleted.🤖 Generated with Claude Code