fix: use npm publish in CI for scoped package auth#41
Merged
Conversation
bun publish with NPM_CONFIG_TOKEN is returning 404 on scoped packages (likely auth not reaching registry). Switch to actions/setup-node + npm publish + NODE_AUTH_TOKEN, which matches standard npm CI flow. Add publishConfig.access public to both packages.
|
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
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
bun publish+NPM_CONFIG_TOKENtonpm publish+actions/setup-node+NODE_AUTH_TOKENpublishConfig.access: publicto both packagesWhy
v0.17.0 publish failed with:
Same error on manual
workflow_dispatchtoday. For scoped packages npm often returns 404 instead of 401 when auth is missing/invalid — so this is likely an expired or revokedNPM_TOKENsecret, not a missing package.May 12 v0.16.0 release failed the same way; a manual re-run succeeded minutes later (possibly after token refresh).
After merge
@runwayml)NPM_TOKENmainat v0.17.0)Test plan