Skip to content

fix CI: upgrade npm for OIDC trusted publishing#4

Merged
deftio merged 1 commit into
mainfrom
feature/fix-ci-publish
Apr 20, 2026
Merged

fix CI: upgrade npm for OIDC trusted publishing#4
deftio merged 1 commit into
mainfrom
feature/fix-ci-publish

Conversation

@deftio

@deftio deftio commented Apr 20, 2026

Copy link
Copy Markdown
Owner

Summary

  • publish.yml: Remove registry-url from setup-node (its .npmrc with empty NODE_AUTH_TOKEN blocks OIDC auth) and add npm install -g npm@latest to get npm 11.5.1+ (required for OIDC trusted publishing)
  • ci.yml: Bump Node matrix from 20.x to 22.x to match publish workflow

Context

The publish workflow has never successfully published — all 14 runs failed with E404 Not Found from npm. Root cause: Node 22 ships with npm 10.9.7, but OIDC trusted publishing requires npm 11.5.1+. Additionally, setup-node with registry-url writes an .npmrc that interferes with OIDC auth.

Test plan

  • CI passes on this PR (Node 22.x, lint, test, build, verify outputs)
  • After merge, trigger publish.yml via workflow_dispatch and verify npm publish succeeds

🤖 Generated with Claude Code

publish.yml: remove registry-url from setup-node (its .npmrc interferes
with OIDC auth) and add npm@latest install to get npm 11.5.1+ which is
required for OIDC trusted publishing support.

ci.yml: bump Node matrix from 20.x to 22.x to match publish workflow.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@deftio deftio merged commit 18e5527 into main Apr 20, 2026
1 check passed
@deftio deftio deleted the feature/fix-ci-publish branch April 20, 2026 04:01
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