fix(ci): upgrade npm to v11 for OIDC trusted publishing#41
Merged
Conversation
actions/setup-node installs Node 20 with npm 10.x, but OIDC trusted publishing requires npm >= 11.5.1. Add explicit npm@11 upgrade step in both release workflows. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
rhuanbarreto
force-pushed
the
fix/trusted-publishing-v2
branch
2 times, most recently
from
4c1873a to
a6c051f
Compare
Ensures consistent Node LTS (Active) and npm versions across dev environments. npm >= 11.5.1 is required for OIDC trusted publishing. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
rhuanbarreto
force-pushed
the
fix/trusted-publishing-v2
branch
from
a6c051f to
7bc0044
Compare
Merged
rhuanbarreto
added a commit
that referenced
this pull request
Mar 3, 2026
* fix(ci): upgrade npm to v11 for OIDC trusted publishing support actions/setup-node installs Node 20 with npm 10.x, but OIDC trusted publishing requires npm >= 11.5.1. Add explicit npm@11 upgrade step in both release workflows. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: pin Node 24 and npm 11.11.0 in .prototools Ensures consistent Node LTS (Active) and npm versions across dev environments. npm >= 11.5.1 is required for OIDC trusted publishing. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
rhuanbarreto
added a commit
that referenced
this pull request
Mar 4, 2026
* fix(ci): upgrade npm to v11 for OIDC trusted publishing support actions/setup-node installs Node 20 with npm 10.x, but OIDC trusted publishing requires npm >= 11.5.1. Add explicit npm@11 upgrade step in both release workflows. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * chore: pin Node 24 and npm 11.11.0 in .prototools Ensures consistent Node LTS (Active) and npm versions across dev environments. npm >= 11.5.1 is required for OIDC trusted publishing. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
npm install -g npm@11step in bothrelease.ymlandrelease-binaries.ymlafteractions/setup-node.prototoolsfor consistent dev environmentsactions/setup-nodeinstalls Node 20 with npm ~10.x, but OIDC trusted publishing requires npm >= 11.5.1. This caused theENEEDAUTHfailure in run #22642341513.Test plan
proto useinstalls Node 22 and npm 11 locally🤖 Generated with Claude Code