fix: publish via npm OIDC trusted publisher#43
Merged
Conversation
Request id-token for GitHub Actions OIDC, drop NPM_TOKEN auth from publish, and use --provenance so npm accepts the configured trusted publisher.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Why
Publish workflow auth works (
npm whoami) butnpm publishfails withEOTP— token path requires 2FA OTP. Trusted publisher is configured on npm forrunwayml/avatars-sdk-react+publish.yml.How it works
id-token: write→ GitHub OIDC token for npmNODE_AUTH_TOKEN/npm whoami— publish uses trusted publisher, not secret tokennpm publish --provenanceon both packagesBefore merge
@runwayml/avatars-react(same repo +publish.yml)Verify
main@runwayml/avatars@0.17.0and@runwayml/avatars-react@0.17.0on npm