Use Node 24 in publish job to fix npm self-upgrade crash#531
Merged
asimgunes merged 1 commit intoeclipse-cdt-cloud:mainfrom May 7, 2026
Merged
Use Node 24 in publish job to fix npm self-upgrade crash#531asimgunes merged 1 commit intoeclipse-cdt-cloud:mainfrom
asimgunes merged 1 commit intoeclipse-cdt-cloud:mainfrom
Conversation
The Update npm step was failing with "Cannot find module 'promise-retry'" on Node 22.22.2 due to npm/cli#9151 — npm@latest cannot self-upgrade from the npm bundled with Node 22.22.2. Node 24's bundled npm already includes the upstream fix from npm/cli#9152. Only the publish job is bumped; CI's Build & Test jobs stay on Node 22. Fixes eclipse-cdt-cloud#530
jreineckearm
approved these changes
May 7, 2026
Contributor
jreineckearm
left a comment
There was a problem hiding this comment.
LGTM as long as CI finishes successfully.
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
2 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.
The
Publish Package to NPMjob has been failing in theUpdate npm (OIDC/provenance support)step becausenpm i -g npm@latestcannot self-upgrade from the npm 10.9.x bundled with Node 22.22.2 (upstream bug npm/cli#9151). This blocked the v1.8.0 release from reaching npm.This PR bumps only the publish job to Node 24, whose bundled npm already includes the upstream fix from npm/cli#9152. CI's Build & Test jobs stay on Node 22 — the integration test matrix (Ubuntu + Windows, GDB breakpoints, async/non-stop, native PTY tests, serialport native builds) is not touched.
The publish job runs only
yarn(which triggersprepublish: yarn build→tsc+esbuild) andnpm publish. No tests, nonativebuildat publish time. The published tarball is JS produced by tsc/esbuild plus.cc/.hsources — runtime-Node-version-independent — so consumers are unaffected by the build host's Node version.A v1.8.1 release preparation PR will follow once this is merged.
Fixes #530