ci: bump publish workflow to Node 22#29
Merged
Merged
Conversation
npm install -g npm@latest now requires Node >=22.22.2, so the release workflow was failing with EBADENGINE on Node 20 before it ever reached the publish step.
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
The v0.7.0 release run failed at the very first step, before installing dependencies or publishing anything:
```
npm error code EBADENGINE
npm error engine Not compatible with your version of node/npm: npm@12.0.1
npm error engine Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
npm error engine Actual: {"npm":"10.8.2","node":"v20.20.2"}
```
`npm install -g npm@latest` now resolves to an npm release that requires Node ≥22, but the workflow pins Node 20. Nothing was published — this fails before
npm publishruns.Fix
Bump
node-versionto22inpublish.ymlonly (this doesn't touchci.yml, which doesn't hit this code path since it never installsnpm@latest).