Enable npm OIDC trusted publisher with provenance#413
Merged
Conversation
Add id-token permission and configure registry URL for npm OIDC authentication. Enable NPM_CONFIG_PROVENANCE to generate package attestations linked to this GitHub Actions workflow.
Pull Request Test Coverage Report for Build 22526726748Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
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.
Summary
Enable GitHub Actions to publish packages to npm using OIDC (OpenID Connect) instead of token-based authentication. Adds provenance attestation to link published packages to this workflow run.
Changes
id-token: writepermission to the release job for OIDC token generationNPM_CONFIG_PROVENANCEWhy
OIDC trusted publishing is more secure than token-based auth. It eliminates the need to manage long-lived secrets and provides cryptographic proof that packages were published by this specific workflow.