feat: enable npm trusted publishing (OIDC) #875
Merged
Conversation
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
Configure the changesets-release job to use npm's Trusted Publishing feature instead of long-lived npm tokens. This uses OpenID Connect (OIDC) for authentication, providing better security through short-lived, workflow-specific credentials. Changes: - Add id-token: write permission for OIDC token generation - Remove NPM_TOKEN secret (no longer needed with trusted publishing) See: https://docs.npmjs.com/trusted-publishers
npm trusted publishing requires npm 11.5.1+, which is bundled with Node.js 24 (npm 11.6.2). Node.js 20 only includes npm 10.8.2.
Contributor
Contributor
Contributor
|
🚀 Deployed on https://6968b884a315d2569f70e653--pglite.netlify.app |
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.
Summary
changesets-releasejob to use npm's Trusted Publishing feature instead of long-lived npm tokensNPM_TOKENsecretWhy Trusted Publishing?
Trusted publishing eliminates the security risks associated with long-lived npm tokens:
Changes
id-token: writepermission to thechangesets-releasejob (required for GitHub Actions to generate OIDC tokens)NPM_TOKENsecret from the workflow (no longer needed with trusted publishing)Configuration
Trusted publishers have been configured on npmjs.com for all packages with:
Documentation
Test plan
Post-merge recommendation
After verifying trusted publishing works correctly, consider restricting token-based publishing access on npmjs.com by navigating to each package's Settings → Publishing access and selecting "Require two-factor authentication and disallow tokens" for maximum security.