Publish to npm via OIDC trusted publishing#148
Merged
Conversation
aurorascharff
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.
The release workflow authenticated with the long-lived
NPM_TOKEN_ELEVATEDsecret, which infra no longer issues — publishing now 403s. Switchesrelease.ymlto npm trusted publishing: OIDC against the trusted publisher configured for this repo, no stored token.id-token: writewas already granted, so this dropsNODE_AUTH_TOKEN, bumps Node to 22 and npm to latest (OIDC needs npm >= 11.5.1), and publishes withnpm publishsincepnpm@9.15.9can't do the OIDC exchange. Provenance is now automatic.