💚 ci: bump node to v24.18.0 so npm@latest installs in the release - #667
Merged
Conversation
npm install -g npm@latest now resolves to npm@12, which requires node ^22.22.2 || ^24.15.0 || >=26 and failed with EBADENGINE against the node pinned in .nvmrc (v24.13.1), breaking the npm publish job.
futjesus
force-pushed
the
fix/pin-npm-version-in-release
branch
from
July 21, 2026 21:04
142efba to
a37039d
Compare
futjesus
changed the title
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
publish-npmjob of the release workflow failed onnpm install -g npm@latest:latestnow resolves to npm@12, which requires node^22.22.2 || ^24.15.0 || >=26and hitEBADENGINEagainst the node pinned in.nvmrc(v24.13.1).Bump
.nvmrcto the current node 24.x (v24.18.0) sonpm@latestkeeps installing — preferable to pinning an older npm line. Applies to every workflow that reads.nvmrc(tests, storybook deploy, release).Context
The
0.1.2-alpha.102release run half-completed: the GitHub Packages job succeeded (the version bump is on main), but the npmjs publish never ran. After this merges, dispatch a new release (e.g.0.1.2-alpha.103) — re-running the failed job would reuse the old workflow snapshot, and re-dispatching the same version would fail thenpm versionbump.Test plan
^24.15.0), so the upgrade step succeeds; trusted publishing continues to work.