Skip to content

fix: upgrade to Node 24 to fix OIDC trusted publishing#243

Merged
tnschneider merged 2 commits into
mainfrom
fix/node-24-for-oidc-publish
Jun 24, 2026
Merged

fix: upgrade to Node 24 to fix OIDC trusted publishing#243
tnschneider merged 2 commits into
mainfrom
fix/node-24-for-oidc-publish

Conversation

@mcarey1590

Copy link
Copy Markdown
Contributor

Summary

  • Upgrades Node.js from 20 to 24 in both CI workflows
  • Fixes the E404 'not in this registry' error during npm publish with OIDC trusted publishing

Root Cause

npm Trusted Publishing (OIDC) requires npm CLI v11.5.1 or later. Node 20 ships with npm v10, which does not support the required OIDC handshake protocol. When the handshake fails silently, the registry treats the request as anonymous, and anonymous PUT requests return a misleading 404 error.

Node 24 (LTS) ships with npm v11, which correctly implements the OIDC handshake and fixes the publish failure.

Reference: npm/cli#8976

Test plan

  • Merge this PR
  • Verify the Merge on Main workflow succeeds and publishes the package

Generated with Devin

mcarey1590 and others added 2 commits June 24, 2026 15:42
npm Trusted Publishing requires npm CLI v11.5.1 or later. Node 20
ships with npm v10, which doesn't support the required OIDC handshake
protocol. This causes a misleading 404 error during npm publish.

Node 24 ships with npm v11, which supports the OIDC handshake. This
fixes the E404 'not in this registry' failure in the release workflow.

Generated with [Devin](https://devin.ai)

Co-Authored-By: Devin <158243242+devin-ai-integration[bot]@users.noreply.github.com>
@tnschneider tnschneider merged commit 75b9949 into main Jun 24, 2026
1 check passed
@tnschneider tnschneider deleted the fix/node-24-for-oidc-publish branch June 24, 2026 20:54
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