Repository navigation
ci(release): publish to npm through trusted publishing - #25
Merged
Merged
Conversation
- Drop the NPM_TOKEN secret from the publish step so npm trades the job's OIDC token for a one-time credential, which attaches provenance by itself; npm stops bypass-2FA tokens from publishing in January 2027
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.
Impact
Releases stop depending on a long-lived npm token. npm restricts granular tokens that bypass 2FA (no account changes now, no direct publishing from January 2027), and the
NPM_TOKENsecret is one of those.Change
The publish step no longer passes
NODE_AUTH_TOKEN, and--provenanceis dropped because trusted publishing attaches provenance itself.id-token: writewas already granted.Verification
npm run checklocally.release.yml, repository LilMGenius/paperthin); the CLI refusesnpm trustfrom a bypass-2FA token.Limits
The first real proof is the next
v*.*.*tag. Until the trust is set on npmjs.com, that release would fail at the publish step.