Adopt npm trusted publishing (OIDC)#571
Merged
Merged
Conversation
Replace token-based npm publishing with trusted publishing. This eliminates the need for long-lived NPM_TOKEN secrets by using GitHub Actions OIDC tokens for authentication. - Add registry-url to setup-node so it configures .npmrc for OIDC - Remove NPM_TOKEN env var from publish step - Remove .npmrc that referenced NPM_TOKEN Closes #542
wjhsf
approved these changes
Mar 12, 2026
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
2 participants
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
registry-urltoactions/setup-nodeso it configures.npmrcfor OIDC authNPM_TOKENenv var from the publish step.npmrcthat referencedNPM_TOKENThis eliminates the need for long-lived
NPM_TOKENsecrets by using GitHub Actions OIDC tokens for authentication. The trusted publisher has been configured on npmjs.com.References