Skip to content

fix(deps): bridge minimatch to 11.0.8 on the advisory's range - #20

Merged
nonagenticai-claude[bot] merged 1 commit into
mainfrom
lane/minimatch-11
Nov 15, 2026
Merged

nonagenticai-claude[bot] merged 1 commit into
mainfrom
lane/minimatch-11

Conversation

@nonagenticai-claude

Copy link
Copy Markdown
Contributor

Why this exists

main is red on the Dependabot Updates job (run 43641403770). This is not a test failure: the updater cannot construct the security update it is asked to make, so it errors instead of opening a PR.

The advisory

  • GHSA-g3hv-75wg-m249 — medium, published 2026-10-30, "minimatch has potential denial of service via globparts amplification"
  • vulnerable range >= 7.0.0, < 11.0.1; first patched 11.0.1
  • updater log: "The latest possible version that can be installed is 10.2.6 … jest: requires minimatch@^9.0.4 (via glob@10.5.0) and minimatch@^10.2.2 (via glob@13.0.7) and minimatch@^10.2.2 (via test-exclude@7.0.2) … The earliest fixed version is 11.0.1."
  • no 10.x is patched, and the only path npm offers downgrades jest 30.5.2 → 29.7.0, which Dependabot refuses.

The change

"overrides": { "minimatch@>=7.0.0 <11.0.1": "^11.0.1" }

in both npm projects (/ and /src — independent lockfiles, independent Dependabot jobs). The range-scoped key moves only the instances the advisory covers, so the 3.x minimatch that eslint 8, @typescript-eslint and mocha resolve is untouched.

Same pattern already merged in the estate: license-validator#17 (flat override) and planka#2 (this range-scoped form).

Lockfile effect (structural diff, no unrelated churn): minimatch 10.2.6 → 11.0.8; the nested 9.0.9 under test-exclude/glob is deduped away; @isaacs/nonrecursive-glob-match (minimatch 11's own dependency) added.

Gates run locally, on 11.0.8

  • root: npm ci → npm run lint (0 errors, 5 pre-existing warnings) → npm test — 177/177 tests, 19/19 suites
  • src: npm ci → jest with --runInBand --forceExit — 177/177. The src npm test script has no --forceExit and hangs on the suite's open handles; that is pre-existing and CI never runs it (the Dockerfile only installs there).
  • npm ls minimatch → 11.0.8 deduped, no invalid; npm audit → no minimatch finding in either tree.

Acceptance after merge

The Dependabot Updates job on the new main must conclude success — a graph-changing push re-runs it (the transition license-validator saw after its override merged). That will be verified, not just the PR checks.

Notes

  • Merging publishes one ghcr image for this repo, by the archetype's design — this is not an npm publish.
  • npm audit still lists glob (GHSA-3g3m-2fjr-6pw4, patched 14.0.2) and deepmerge (low). Neither is in this repo's Dependabot job set (the failing job's only target was minimatch), so they are out of scope here.

🤖 Generated with Claude Code

GHSA-g3hv-75wg-m249 (medium, vulnerable >=7.0.0 <11.0.1, patched 11.0.1) cannot be
resolved in range: jest 30.5.2 pulls minimatch ^9.0.4 via glob@10.5.0 and ^10.2.2 via
glob@13.0.7/test-exclude, and no 10.x is patched. Dependabot therefore refuses the only
path (a jest downgrade) and errors instead of opening a PR, which reds main.

The range-scoped override resolves every in-range instance to 11.0.8 and leaves the 3.x
instances (eslint 8, @typescript-eslint, mocha) alone, as the advisory does not cover them.
Same pattern as license-validator#17 and planka#2.

Co-Authored-By: Claude Code <noreply@anthropic.com>
@nonagenticai-claude
nonagenticai-claude Bot merged commit 0663d8c into main Nov 15, 2026
7 checks passed
@nonagenticai-claude
nonagenticai-claude Bot deleted the lane/minimatch-11 branch November 15, 2026 10:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant