ci: pin slim-publish npm to v11 to fix EBADENGINE#698
Merged
Conversation
npm@latest now resolves to [email protected], which requires node ^22.22.2 || ^24.15.0 || >=26.0.0. CI runs node v22.14.0, so the global install failed with EBADENGINE and the slim publish step exited 1. Pin to npm@^11.5.1 (matching the step's stated intent) so it stays compatible with the CI node version. Co-Authored-By: Claude Opus 4.8 <[email protected]>
Debugger022
self-requested a review
July 14, 2026 12:18
Debugger022
approved these changes
Jul 14, 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.
Problem
The
releasejob's Publish slim package step fails with:```
npm error code EBADENGINE
npm error notsup Required: {"node":"^22.22.2 || ^24.15.0 || >=26.0.0"}
npm error notsup Actual: {"npm":"10.9.2","node":"v22.14.0"}
```
Failing run: https://github.com/VenusProtocol/venus-protocol/actions/runs/29325391520/job/87060361905
The main package publishes fine (
10.3.0-dev.2todevelop); only the slim step fails. It runsnpm install -g npm@latest, which now resolves to [email protected]. npm 12 requires node^22.22.2 || ^24.15.0 || >=26.0.0, but CI provides nodev22.14.0, so the global install aborts withEBADENGINEand the step exits 1.Fix
Pin the global npm install to the v11 line (
npm@^11.5.1), matching the step's own stated intent ("Ensure npm 11.5.1 or later"). This keeps it compatible with the CI node version and avoids being dragged onto npm 12 by@latest.🤖 Generated with Claude Code