Skip to content

Fix Trusted Publisher auth and bump to 0.2.2#16

Merged
sdserranog merged 2 commits intomainfrom
sdserranog/fix-npm-trusted-pub
Mar 5, 2026
Merged

Fix Trusted Publisher auth and bump to 0.2.2#16
sdserranog merged 2 commits intomainfrom
sdserranog/fix-npm-trusted-pub

Conversation

@sdserranog
Copy link
Copy Markdown
Contributor

Summary

  • Removes registry-url from actions/setup-node in the release workflow — it was creating an .npmrc with an empty NODE_AUTH_TOKEN placeholder that overrode the OIDC exchange needed for Trusted Publishers
  • Bumps version to 0.2.2 to trigger the release on merge

Test plan

  • Merge triggers the release workflow
  • npm publish --provenance succeeds via OIDC auth
  • npm view @arcadeai/create-agent version returns 0.2.2

🤖 Generated with Claude Code

sdserranog and others added 2 commits March 4, 2026 20:24
actions/setup-node with registry-url creates an .npmrc containing
//registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN}. Since we use
Trusted Publishers (OIDC) and don't set NODE_AUTH_TOKEN, npm sends
an empty token instead of doing the OIDC exchange, causing a 404.

Removing registry-url lets npm fall through to OIDC auth automatically.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@sdserranog sdserranog merged commit 0159b67 into main Mar 5, 2026
@sdserranog sdserranog deleted the sdserranog/fix-npm-trusted-pub branch March 5, 2026 00:25
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