fix(ci): use Node.js 24 for OIDC trusted publishing support#17
Merged
talissoncosta merged 1 commit intomainfrom Feb 6, 2026
Merged
fix(ci): use Node.js 24 for OIDC trusted publishing support#17talissoncosta merged 1 commit intomainfrom
talissoncosta merged 1 commit intomainfrom
Conversation
Node.js 22 ships with npm v10 which has a bug with OIDC trusted publishing. Node.js 24 ships with npm v11 which fixes this issue. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Zaimwa9
approved these changes
Feb 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Root Cause
Node.js 22 ships with npm v10 which has a bug causing misleading "Access token expired" errors during OIDC authentication with npm registry.
Test Results
npm install -g npm@latestworkaround