fix(ci): Pin npm to v11 for Node 20 compatibility in release workflow - #1097
Merged
Conversation
npm 12 dropped support for Node 20 (requires ^22.22.2 || ^24.15.0 || >=26.0.0), so 'npm install -g npm@latest' now fails on the Node 20 runner pinned by .nvmrc. Pin to npm@11, which supports Node 20 and still provides trusted publishing (added in npm 11.5.1). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Qan7ZWehTJKYRDSRSEDqk
avallete
enabled auto-merge (squash)
August 6, 2026 09:56
avallete
changed the title
mandarini
approved these changes
Aug 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
3 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
Updates the npm version constraint in the release workflow to pin to npm v11 instead of always installing the latest version. This ensures compatibility with Node 20, which is the minimum supported version for this project.
Changes
npm install -g npm@latesttonpm install -g npm@11in the release workflowDetails
The release workflow previously installed the latest npm version globally, which could cause issues since npm 12 dropped support for Node 20. By pinning to npm v11, we ensure the workflow uses a version that:
https://claude.ai/code/session_018Qan7ZWehTJKYRDSRSEDqk