build: Use OIDC for npm publishing#5609
Merged
Conversation
Switch from NPM_TOKEN secret to GitHub OIDC for npm authentication. This is more secure and doesn't require token rotation. Changes: - Add id-token: write permission to publish-js job - Use --provenance flag for OIDC-based publishing - Remove NPM_TOKEN secret usage 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <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
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.
Summary
NPM_TOKENsecret to GitHub OIDC for npm authenticationChanges
id-token: writepermission topublish-jsjob--provenance --access publicflags for OIDC-based publishingNPM_TOKENsecret usageContext
The 0.13.8 npm release failed because the NPM_TOKEN expired. OIDC eliminates this failure mode.
Test plan
🤖 Generated with Claude Code