Skip to content

fix: add registry-url for npm Trusted Publishing#116

Merged
nastassiafulconis merged 4 commits intomainfrom
nastassiafulconis/fix-npm-publish
Feb 17, 2026
Merged

fix: add registry-url for npm Trusted Publishing#116
nastassiafulconis merged 4 commits intomainfrom
nastassiafulconis/fix-npm-publish

Conversation

@nastassiafulconis
Copy link
Collaborator

Summary

  • Adds registry-url: 'https://registry.npmjs.org' to the setup-node step in the release workflow
  • Without this, setup-node doesn't create the .npmrc file needed for OIDC token exchange, causing ENEEDAUTH errors during changeset publish

Test plan

  • Merge and verify the Release workflow publishes scope3@2.0.0 to npm successfully

🤖 Generated with Claude Code

Without registry-url, setup-node doesn't create the .npmrc file
needed for OIDC auth to work. This caused ENEEDAUTH errors during
changeset publish.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@nastassiafulconis nastassiafulconis requested a review from a team February 17, 2026 22:35
nastassiafulconis and others added 3 commits February 17, 2026 23:38
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Upgrade Node.js 20 → 22 (npm Trusted Publishing requires Node 22.14.0+)
- Add registry-url for OIDC token exchange
- Add publishConfig.provenance for changeset publish compatibility
- Remove redundant npm@latest upgrade (Node 22 ships with npm 11+)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Node 22 may not ship with npm 11.5.1+ which is the minimum
for Trusted Publishing.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@nastassiafulconis nastassiafulconis enabled auto-merge (squash) February 17, 2026 23:05
@nastassiafulconis nastassiafulconis merged commit b852335 into main Feb 17, 2026
6 checks passed
@nastassiafulconis nastassiafulconis deleted the nastassiafulconis/fix-npm-publish branch February 17, 2026 23:30
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.

2 participants