Fix npm publish workflow (Node 22, pin npm@12) - #25
Merged
Conversation
npm@latest is now 12.x, which requires Node >=22.22.2 and dropped Node 20 support, breaking the "Upgrade npm for Trusted Publishing" step (npm ci EBADENGINE) and blocking the v1.1.0 release. Node 20 is also EOL. Bump CI (and .nvmrc for local parity) to Node 22.x and pin npm to 12 so a future npm engine bump can't silently break publishing. Co-Authored-By: Claude Opus 4.8 <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.
Background
The v1.1.0 Publish to npm run failed before publishing: the latest npm now requires Node >=22.22.2, but CI still ran the EOL Node 20, so the Trusted Publishing upgrade step errored out.
Change
Move CI and local dev to Node 22, and pin the publish step to a fixed npm major so a future npm engine bump can't silently break releases again.
Test Plan
Build check green on this PR; after merge, re-point the v1.1.0 tag to re-trigger publish.