Skip to content

ci(spec): remove obsolete gen/node/.npmrc (trusted publishing)#205

Merged
scarmuega merged 1 commit into
mainfrom
ci/drop-node-npmrc
May 19, 2026
Merged

ci(spec): remove obsolete gen/node/.npmrc (trusted publishing)#205
scarmuega merged 1 commit into
mainfrom
ci/drop-node-npmrc

Conversation

@scarmuega
Copy link
Copy Markdown
Member

Context

Follow-up to #204. That PR moved the node package to OIDC trusted publishing and removed NODE_AUTH_TOKEN from the workflow, but gen/node/.npmrc (added in #61 for the old token flow) was left behind.

With NODE_AUTH_TOKEN now unset, its //registry.npmjs.org/:_authToken=${NODE_AUTH_TOKEN} line injects an empty token that overrides the OIDC credential — publish fails with a masked 404. This was reproduced locally and is the latent CI failure #204 didn't fully resolve.

Change

git rm gen/node/.npmrc. All three lines are now either redundant or harmful:

  • registry= / @utxorpc:registry= — only restate npm defaults.
  • _authToken=${NODE_AUTH_TOKEN} — breaks OIDC auth.

Trusted publishing needs no .npmrc (npm ≥ 11.5.1 handles auth via OIDC). npm never includes .npmrc in the published tarball, so no effect on consumers.

Refs #204.

🤖 Generated with Claude Code

This file was added in #61 for token-based npm publishing. Since #204
switched the node package to OIDC trusted publishing, it is no longer
needed and is actively harmful: it pins
`_authToken=${NODE_AUTH_TOKEN}`, and with that env var now unset in
CI the empty token overrides the OIDC credential and the publish fails
with a 404.

The other two lines (registry and @utxorpc:registry) only restate
npm defaults. npm never includes .npmrc in the published tarball, so
removing it has no effect on consumers.

Refs #204.
@scarmuega scarmuega merged commit 7814e49 into main May 19, 2026
@scarmuega scarmuega deleted the ci/drop-node-npmrc branch May 19, 2026 16: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.

1 participant