fix: use allowlisted setup-node SHA for npm publish#42
Merged
Conversation
Use sdk-node's enterprise-allowed setup-node commit and verify auth with npm whoami before build.
|
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
#41 merged but Publish workflow hits enterprise action allowlist —
setup-node@499817a2…blocked. sdk-node publish uses allowlisted3235b876…(v3.9.1).Also moves
NODE_AUTH_TOKENonto setup-node step (writes.npmrc) and addsnpm whoamifail-fast before build.Verify
mainVerify npm authstep prints npm username@runwayml/avatars@0.17.0and@runwayml/avatars-react@0.17.0land on npm