Skip to content

fix: use npm publish in CI for scoped package auth#41

Merged
robinandeer merged 1 commit into
mainfrom
fix/npm-publish-auth
Jul 6, 2026
Merged

fix: use npm publish in CI for scoped package auth#41
robinandeer merged 1 commit into
mainfrom
fix/npm-publish-auth

Conversation

@robinandeer

Copy link
Copy Markdown
Collaborator

Summary

  • Switch publish workflow from bun publish + NPM_CONFIG_TOKEN to npm publish + actions/setup-node + NODE_AUTH_TOKEN
  • Add publishConfig.access: public to both packages

Why

v0.17.0 publish failed with:

404 Not Found: https://registry.npmjs.org/@runwayml%2favatars
'@runwayml/avatars@0.17.0' does not exist in this registry

Same error on manual workflow_dispatch today. For scoped packages npm often returns 404 instead of 401 when auth is missing/invalid — so this is likely an expired or revoked NPM_TOKEN secret, 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

  1. Regenerate npm Automation token at https://www.npmjs.com/settings/~your-user/tokens (needs publish on @runwayml)
  2. Update GitHub repo secret NPM_TOKEN
  3. Re-run publish: Actions → Publish → Run workflow (on main at v0.17.0)

Test plan

  • Merge + rotate token + workflow_dispatch → both packages publish

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.
@vercel

vercel Bot commented Jul 6, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
avatars-playground Ready Ready Preview, Comment Jul 6, 2026 5:09pm

Request Review

@robinandeer robinandeer merged commit 37872f5 into main Jul 6, 2026
6 checks passed
@robinandeer robinandeer deleted the fix/npm-publish-auth branch July 6, 2026 17:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant