You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Update minimatch past GHSA-g3hv-75wg-m249 (Dependabot alert 4) #136
Josh asked for this on 2026-11-15, covering this alert only: raise minimatch to the first patched version in package-lock.json through one reviewed pull request, installing only in the builder's own working copy. If a patched minimatch cannot be reached without moving another package (a parent package pins an older major), stop and report which package and why, and do not move it. No other package moves.
Acceptance criteria
package-lock.json resolves every minimatch at or above 11.0.1, or the PR records which parent package pins an older major and the ticket stops there.
No other package version changes in package-lock.json or package.json unless the PR states why it was unavoidable.
npm audit output for minimatch is recorded in the PR, and the Dependabot alert reads fixed once the PR merges.
The repository's local checks pass.
Decision
Decided 2026-11-17: dismiss the alert as tolerable, and let the fix arrive upstream. minimatch is development scope and runs only inside the test tooling, on patterns the repository itself writes, so nothing outside the repository reaches it. The patched editorconfig 4 and glob 14 are accepted by no js-beautify release yet, and beautifier/js-beautify#2569 moves js-beautify onto minimatch 11. Once a js-beautify release carries it, a lockfile-only update clears the alert, and Dependabot opens that update itself. Rejected options: overrides forcing editorconfig 4 and glob 14 outside js-beautify's declared ranges, downgrading @vue/test-utils to 2.4.11, and leaving the alert open until the release. The alert is dismissed by the maintainer. No package moves under this ticket.
Stopped under this ticket's Scope: no patched minimatch can be reached without moving another package.
Read from package-lock.json on main at 05cb51f and from the npm registry on 2026-11-16:
The lock holds one minimatch, node_modules/minimatch at 10.2.6 (development scope). The advisory's first patched version is 11.0.1, and no 10.x release is patched: the vulnerable range is >= 7.0.0, < 11.0.1, and the newest 10.x is 10.2.6.
Both come from js-beautify2.0.3, which requires editorconfig^3.0.2 and glob^13.0.6. 2.0.3 is the latest js-beautify, so no release of it accepts the patched versions.
js-beautify comes from @vue/test-utils (^2.0.0, latest 2.6.0), which package.json requires as ^2.5.1 for the Control Panel component tests.
So the parent that pins the older major is js-beautify, through editorconfig and glob. Nothing was changed. The routes that remain each move something this ticket does not allow:
an npm overrides entry forcing editorconfig 4 and glob 14 under js-beautify, outside the ranges it declares;
waiting for a js-beautify release that accepts them;
dismissing the alert as development-only, since minimatch runs only in the test tooling.
Activity
bpmore commentedon Nov 17, 2026
Stopped under this ticket's Scope: no patched
minimatchcan be reached without moving another package.Read from
package-lock.jsononmainat05cb51fand from the npm registry on 2026-11-16:minimatch,node_modules/minimatchat10.2.6(development scope). The advisory's first patched version is11.0.1, and no10.xrelease is patched: the vulnerable range is>= 7.0.0, < 11.0.1, and the newest10.xis10.2.6.editorconfig3.0.2requiresminimatch~10.2.4. No3.xrelease takes 11 (3.0.1requires10.0.1).editorconfig4.0.1takes~11.0.5.glob13.0.7requiresminimatch^10.2.2. No13.xrelease takes 11.glob14.xtakes^11.0.0.js-beautify2.0.3, which requireseditorconfig^3.0.2andglob^13.0.6.2.0.3is the latestjs-beautify, so no release of it accepts the patched versions.js-beautifycomes from@vue/test-utils(^2.0.0, latest2.6.0), whichpackage.jsonrequires as^2.5.1for the Control Panel component tests.So the parent that pins the older major is
js-beautify, througheditorconfigandglob. Nothing was changed. The routes that remain each move something this ticket does not allow:overridesentry forcingeditorconfig4 andglob14 underjs-beautify, outside the ranges it declares;js-beautifyrelease that accepts them;minimatchruns only in the test tooling.