build: require Node 24.19.0 and npm 11.17.0 - #12
Merged
yokuze merged 1 commit intoAug 18, 2026
Merged
Conversation
velocitysystems
force-pushed
the
build/node-24.19-npm-11.17-min-release-age
branch
from
August 15, 2026 20:18
d012553 to
6dfe90c
Compare
velocitysystems
force-pushed
the
build/node-24.19-npm-11.17-min-release-age
branch
from
August 15, 2026 20:29
6dfe90c to
2bd0d6c
Compare
seanmonstar
approved these changes
Aug 15, 2026
velocitysystems
force-pushed
the
build/node-24.19-npm-11.17-min-release-age
branch
from
August 18, 2026 10:09
2bd0d6c to
d3875aa
Compare
yokuze
approved these changes
Aug 18, 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
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.
Why
npm's
min-release-age/min-release-age-excluderefuse to install package versions thathave not been public for a given number of days — a cheap, high-leverage mitigation against
registry compromises like Shai-Hulud/ChainDrop, which arrive as freshly published versions of
otherwise-trusted packages.
Those flags require npm >= 11.14.0. This repo pins npm 11.8.0 via
check-node-version, sothey are currently unavailable. Node 24.19.0 (Krypton LTS) bundles npm 11.17.0 exactly, so
a single
.nvmrcbump delivers both.This PR is only the toolchain upgrade that makes those flags usable. It deliberately does not
set any release-age policy itself, so
.npmrcis untouched.What changed
.nvmrc24.13.1→24.19.0package.jsoncheck-node-version --npm 11.17.0No
.npmrc, dependency, or lockfile changes.Verification
.nvmrcbump alone pins both versions.min-release-ageandmin-release-age-exclude(added innpm 11.14.0), so the upgrade achieves its stated purpose.