Repository navigation
chore(deps): patch minimatch 10.x in the lockfile, with glob 14 to match - #1537
Conversation
…tch (#1536) minimatch 10.2.6 sits in a ReDoS advisory range (patched in 11.0.1); an override moves it to 11.0.3. glob 13.0.6, used by @sentry/bundler-plugins to find source maps, matches nothing with minimatch 11, so glob 13 moves to 14.0.3, which depends on minimatch 11 and is outside glob's own advisory. The lockfile has no follow-redirects. minimatch 3.1.5 from ESLint 9 has no patched 3.x and stays. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
If your organization's extra usage balance is empty, an organization admin can add extra usage credits at claude.ai/admin-settings/usage. If its monthly spend limit was reached, an admin can raise it on the same page. If neither applies, contact Anthropic support.
Once extra usage is available, someone with write access to this repository can comment @claude review on this pull request to trigger a review.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Dependency version overrides package.json |
The configuration adds minimatch@^10 → ^11.0.1 and glob@^13 → ^14.0.3 overrides. The existing js-yaml override remains unchanged. |
Estimated code review effort: 2 (Simple) | ~5 minutes
Change: Other · Severity of issue fixed: Medium
Suggested reviewers: dos
Merge Risk: 
Minimal · up to f4b0b
-
No merge-blocking issue is established for these dependency overrides. Merge after the normal build and test checks pass.
Pre-merge checks: 
3 · 
1
-
Failed checks: 1 inconclusive Passed checks: 3 passed-
Full details: Out of Scope Changes check
-
Explanation
The reported changes are limited to dependency overrides and the lockfile. The minimatch and glob changes support
#1536by addressing the advisory and preserving Sentry glob behavior. No unrelated change is demonstrated.
Full details: Description check
-
Explanation
The description is detailed and directly addresses the dependency changes, security rationale, affected packages, compatibility risks, validation results, and linked issue. It does not use the repository template headings and omits the explicit checklist, affected areas, reviewers, and optional screenshots, but the required technical information is mostly present.
-
Full details: Linked Issues check
-
Explanation
For
#1536, the PR reports the required minimatch override, glob compatibility fix, removal of the minimatch 10.x audit finding, absence of follow-redirects, retention of minimatch 3.1.5, and passing lint and typecheck. The PR reports that unit and E2E tests run in CI, but it does not establish that both checks passed. The lockfile is excluded from review, so its resolved versions rely on the PR report.Resolution
Provide reviewable evidence that the unit and E2E checks pass, and confirm the lockfile resolves minimatch 11.0.3 and glob 14.0.3.
-
Finishing Touches
-
Generate unit tests (beta)
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
fast-uri 3.1.8 is inside a newer advisory range (<3.1.9). After this, pnpm audit lists only minimatch 3.1.5 from ESLint 9, which has no patched 3.x. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Closes #1536
Problem
pnpm-lock.yamlresolved minimatch 10.2.6. That is inside a moderate ReDoS (regex denial of service) advisory range, patched in 11.0.1. It is reached through glob 13 (@sentry/bundler-plugins) and the typescript-eslint (@typescript-eslint) path.Change (
package.jsonpnpm.overrides, lockfile)"minimatch@^10": "^11.0.1", the same entry Rate-Services uses (RS#825). It resolves to minimatch 11.0.3."glob@^13": "^14.0.3", which is new and needed:glob('*.json')returns[], against 4 files with minimatch 10.@sentry/bundler-plugins(core/glob.js,globFiles) uses to find build files and source maps. So the minimatch override alone would quietly break the Sentry source-map step at build time, while lint, tests and E2E all stay green.minimatch ^11.0.2. It keeps theglob()API that Sentry calls, and it is outside glob's own advisory range (>=9.0.0 <=14.0.1), whichpnpm auditalso listed for 13.0.6."fast-uri@>=3.0.0 <3.1.9": "^3.1.9": the existing override moves up one patch, from 3.1.8 to 3.1.9, because 3.1.8 is inside a newer advisory range (<3.1.9). The PO asked for it in this PR, as the same kind of XS security change.@isaacs/nonrecursive-glob-match1.0.3, a minimatch 11 dependency by the same author.Not changed
pnpm auditstill lists it (moderate,<11.0.1).Checks
pnpm audit:Sentry's own helper, run against the installed packages:
globFiles(['apps/web/e2e/*.spec.ts', '*.json'])returns 90 files (86 specs and 4 JSON files);Lint and types:
turbo lint --force(no cache): 4 of 4 tasks pass. ESLint runs typescript-eslint (@typescript-eslint), which also uses minimatch.apps/webtsc is clean.Unit tests and E2E run in CI.
Review
@typescript-eslint/typescript-estreeand glob 13. typescript-estree only callsminimatch(path, pattern, {dot})forallowDefaultProject, which no config here sets.makeRe,ASTand some prototype helpers. Neither consumer uses them.root, extglob/**/*.js?(\?*)?(#*),ignore) the same as glob 13 with minimatch 10.🤖 Generated with Claude Code