ci(release): switch to npm OIDC trusted publishing - #3
Merged
Merged
Conversation
Replace NPM_TOKEN secret with npm provenance via GitHub OIDC. This uses the trusted publisher configured in npm instead of a long-lived token.
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
1 participant
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.
What/Why?
Replace the
NPM_TOKENsecret with OIDC trusted publishing, since npm is already configured with GitHub Actions as a trusted publisher.Changes:
actions/setup-nodewithregistry-urlto configure the npm auth flowNPM_CONFIG_PROVENANCE: trueso published packages get provenance attestationNODE_AUTH_TOKEN/NPM_TOKENreference — OIDC handles auth via theid-token: writepermissionTesting
No functional change until a changeset is merged. The release workflow will be exercised on the first version bump.