Use npm trusted publishing (remove NODE_AUTH_TOKEN)#11
Merged
Conversation
Remove NODE_AUTH_TOKEN since the workflow uses OIDC trusted publishing (id-token: write + --provenance). Upgrade npm to ensure a version that supports trusted publishing.
colinhemphill
approved these changes
Jun 24, 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
The
npm_release.yamlworkflow already grantsid-token: writeand publishes with--provenance, which means it uses npm's trusted publishing via OIDC. With trusted publishing, no long-lived auth token is needed, so theNODE_AUTH_TOKEN/secrets.NPM_TOKENis redundant.Changes
NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}env from thenpm publishstep.npm install -g npm@latestbefore publishing, since trusted publishing requires npm>= 11.5.1(newer than the version bundled with Node 22.x).Notes
This requires that a trusted publisher for this package be configured on npmjs.com (linking the repo +
npm_release.yamlworkflow). Once that's in place, theNPM_TOKENsecret can be removed from the repo.