Repository navigation
Align npm release-age gate with the Dependabot cooldown - #414
Merged
Vladimir Morozov (vmoroz) merged 1 commit intoNov 18, 2026
Merged
Conversation
Dependabot's grouped npm version update failed with NoChangeError for @babel/generator and @babel/parser. When a package is a transitive dependency of an npm project, Dependabot picks the new version by running `npm update` without an age limit, but then rewrites the lockfile with `--min-release-age=<cooldown>`. A release younger than the 8-day cooldown is proposed, the rewrite leaves the lockfile unchanged, and the run fails. Set min-release-age=8 in each npm project's .npmrc. npm applies it in both steps, so they agree. Dependabot adds its own flag only when the cooldown exceeds this value, and security updates still override it with --min-release-age=0. Yarn projects already behave this way through npmMinimalAgeGate in .yarnrc.yml. npm 11.10 and newer also apply the gate to local and CI restores. Older npm ignores it and prints an "Unknown project config" warning.
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues remain for the change aligning npm’s release-age gate with the existing eight-day cooldown.
No open issues 🎉
What changed in this PR
Aligns npm’s release-age gate with the existing eight-day Dependabot cooldown and Yarn setting, addressing inconsistent transitive dependency selection that caused grouped updates to fail.
Changes:
- Adds
min-release-age=8to all eight npm projects’.npmrcfiles. - Updates package-feed documentation and the Dependabot comment to identify the settings that must stay aligned and explain older npm behavior.
| File | Description |
|---|---|
unittests/NodeApi/test/.npmrc |
Adds the eight-day gate for Node-API tests. |
tools/hcdp/.npmrc |
Adds the eight-day gate for HCDP tooling. |
tools/fork-sync/.npmrc |
Adds the eight-day gate for fork-sync tooling. |
external/node-api-cts/.npmrc |
Adds the eight-day gate for Node-API conformance tests. |
benchmarks/widgets/single-file/es5/.npmrc |
Adds the eight-day gate for single-file widget benchmarks. |
benchmarks/widgets/original/es5/.npmrc |
Adds the eight-day gate for original widget benchmarks. |
benchmarks/raytracer/original/.npmrc |
Adds the eight-day gate for raytracer benchmarks. |
.github/dependabot.yml |
Updates the comment to reference both npm and Yarn age gates. |
.ado/scripts/README.md |
Documents alignment, transitive resolution, and older npm behavior. |
.ado/scripts/.npmrc |
Adds the eight-day gate for build and CI tooling. |
Review effort: Balanced
Benchmark ResultsTotal benchmarks: 204 Inputs: baseline/baseline.json, bench_result.json v8 (6176ms, 4413ms) -28.6%
test-suites (317886ms, 249132ms) -21.6%
micros (60876ms, 48174ms) -20.9%
jit-benches (8563ms, 5382ms) -37.1%
many-subclasses (73437ms, 63646ms) -13.3%
map-objects (3627ms, 1493ms) -58.8%
map-strings (4335ms, 1724ms) -60.2%
nbody (3448ms, 2336ms) -32.2%
string-switch (6503ms, 4765ms) -26.7%
raytracer (5608ms, 4413ms) -21.3%
MiniReact (30332ms, 16581ms) -45.3%
widgets (12934ms, 10230ms) -20.9%
|
Vladimir Morozov (vmoroz)
enabled auto-merge (squash)
November 18, 2026 04:15
Julio César Rocha (JunielKatarn)
approved these changes
Nov 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.
Summary
The grouped npm Dependabot update
(run 43036355131)
failed with
NoChangeErrorfor@babel/generatorand@babel/parserin three npmprojects. Both packages are direct dependencies of other monitored projects, so
Dependabot also checks them where they are only transitive. For a transitive npm
dependency, Dependabot picks the new version with
npm updateand no age limit, thenrewrites the lockfile with
--min-release-age=8taken from the cooldown. Babel 7.29.13was less than 8 days old, so the rewrite changed nothing and the run failed. The Yarn
projects in the same run did not fail:
npmMinimalAgeGate: "8d"in.yarnrc.ymlapplies to both steps.
min-release-age=8in each npm project's.npmrc, so npmuses the same limit in both Dependabot steps. Dependabot adds its own flag only when
the cooldown is longer, and security updates still override the gate with
--min-release-age=0.dependabot.ymland "Package feeds" in.ado/scripts/README.mdnow name all three settings that must stay aligned.npm 11.10 and newer (Node 24 currently bundles 11.19.1) also apply the gate to local
and CI restores.
npm cithen rejects a locked version younger than 8 days, one daylonger than the proxy already withholds new versions. Older npm ignores the setting and
prints an "Unknown project config" warning.
Test Plan
Local validation through the anonymous PackageFeedProxy:
.\dev npm-source-lint: passed, 13 projects, 0 violations. Its.ado/scriptsrestore with npm 11.8.0 printed the expected warning and succeeded.
a copy of
unittests/NodeApi/test:npm update @babel/generator --force --ignore-scripts --package-lock-only --allow-git=all --allow-remote=all.Babel 7.29.13 is now 13 days old, so a 14-day gate recreates the run's timing:
main: locked 7.29.13;--min-release-age=14, as the writer runs it: kept 7.29.12, the mismatchthat failed the run;
min-release-age=14in.npmrcand no flag: kept 7.29.12, so both stepsagree;
.npmrc: locked 7.29.13, so the pending update now goesthrough.
npm ci --ignore-scriptswith npm 11.20.0 and the committed gate: passed for alleight npm projects. From an empty cache,
unittests/NodeApi/testtook 5.4 s withthe gate and 7.4 s without it.
The next scheduled Dependabot npm run confirms the fix after merge.
Microsoft Reviewers: Open in CodeFlow