Repository navigation
fix: remediate the minimatch Dependabot alert (2026-11, wave 2) - #47
Merged
Merged
Conversation
…wave 2) minimatch < 11.0.1 (GHSA, medium) came from glob 10 (test-exclude 7), glob 13 (jest 30: @jest/reporters, jest-config, jest-runtime), test-exclude 7 and @typescript-eslint/typescript-estree 8. Scoped Yarn 1 resolutions move every glob consumer to glob ^14.0.3 and the direct minimatch users to ^11.0.1, so minimatch 11 never runs under glob 10/11/13 (which silently matches nothing). Only glob 14.0.4 + minimatch 11.0.5 remain (plus minimatch 3 for glob 7). Signed-off-by: Florent BOURASSE <fbourasse@jahia.com>
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
Fixes the root minimatch alert with the glob 14 method (wave 2, 2026-11).
tests/and the/testsentry of.github/dependabot.ymlare untouched. No root Dependabot PR is open; the/testsgroup #45 is validated separately by the e2e harness.Change
minimatch
>= 7.0.0, < 11.0.1(alert #140, medium, fixed in 11.0.1) came from four consumers:test-exclude7)@jest/reporters,jest-config,jest-runtime)test-exclude7 itself@typescript-eslint/typescript-estree8glob 10, 11 and 13 combined with minimatch 11 silently match nothing. So every glob consumer is moved to glob 14, and only the direct minimatch users go to 11. Scoped Yarn 1 resolutions added to the root
package.json:Lockfile result: a single glob ≥ 10 (14.0.4, with minimatch 11.0.5), plus glob 7 / minimatch 3 for the old rimraf/eslint chain.
Alerts
deepmerge4.3.1 (low, via jest-config 30). It has no patched version.tests/alerts (out of scope): extract-zip ×2 (no patched version).Test plan
mvn -B clean installon JDK 11 (frontend-maven-plugin 1.15.4) in a freshgit worktree: BUILD SUCCESS, 44 tests. The default branch gives the same result.Import-Package/Require-Capability, default branch vs this branch): identical.globSync('*')> 0.rimraf --glob(rimraf 6) deletes the matching files in a dummy directory.jest --coverage(which uses test-exclude with glob 14): 5/5 tests. The coverage table is identical to main (52.17 / 41.46 / 22.22 / 53.33), so test-exclude still finds the source files.yarn lintpasses.