Skip to content

ci: drop registry-url so OIDC isn't shadowed by placeholder token - #20

Merged
Suprhimp merged 1 commit into
masterfrom
ci-oidc-fix
Jul 2, 2026
Merged

ci: drop registry-url so OIDC isn't shadowed by placeholder token#20
Suprhimp merged 1 commit into
masterfrom
ci-oidc-fix

Conversation

@Suprhimp

@Suprhimp Suprhimp commented Jul 2, 2026

Copy link
Copy Markdown
Member

Trusted Publisher is now connected, but the release still 404'd because setup-node's registry-url writes a placeholder _authToken into .npmrc (seen as NODE_AUTH_TOKEN: XXXXX-XXXXX-XXXXX-XXXXX in the run), which npm uses instead of OIDC.

Removing registry-url leaves no token in .npmrc, so npm falls through to OIDC Trusted Publishing. Default registry is registry.npmjs.org regardless.

Merging triggers the Release job → publishes the pending 1.1.0 via OIDC (+ git tag + GitHub release).

🤖 Generated with Claude Code

setup-node's registry-url writes a placeholder _authToken into .npmrc,
which npm uses instead of OIDC — causing E404 on publish. Trusted
Publishing requires no token in .npmrc; the default registry is
registry.npmjs.org anyway.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@Suprhimp
Suprhimp merged commit 9b9ccb7 into master Jul 2, 2026
@Suprhimp
Suprhimp deleted the ci-oidc-fix branch July 3, 2026 07:37
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