feat: enable trusted publishing for npm packages #999
Merged
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
Switch npm publishing from token-based authentication to OIDC-based trusted publishing.
Changes
npm-tokensecret requirement from workflows and publish actionid-token: writepermission for OIDC authentication--provenanceflag andNODE_AUTH_TOKENenvironment variablePost-merge: Configure on npmjs.com
Package Settings → Trusted Publisher → GitHub Actions:
auth0auth0-reactrelease.ymlreleaseBenefits