fix(ci): run the publish job on Node 24 - #95
Merged
Merged
Conversation
The job pinned Node 20 and then ran `npm install -g npm@latest`. npm 12 requires Node ^22.22.2 || ^24.15.0 || >=26.0.0, so that step failed with EBADENGINE and the release never published. A recent npm is needed here for OIDC trusted publishing, so the Node version moves rather than the npm version.
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
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.
The publish job pinned
node-version: '20'and then rannpm install -g npm@latest. npm 12 requires Node^22.22.2 || ^24.15.0 || >=26.0.0, so that step failed:The release therefore never reached
npm publish. A recent npm is required here for OIDC trusted publishing, so the Node version moves rather than the npm version.This only affects the publish job. The test matrix still covers Node 20 and 22.