Repository navigation
chore(deps): override glob and minimatch past the open advisories - #826
Merged
Merged
Conversation
jennifer-takagi
approved these changes
Nov 12, 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.
No Jira ticket. Closes Dependabot alerts #91 (minimatch).
Proposed changes
overrides, the same pair maverick and ots-base already carry:"glob@>=9.0.0 <14.0.2": "^14.0.4"and"minimatch@>=7.0.0 <11.0.1": "^11.0.5". The rest of the lockfile diff is the old glob 10/13 and minimatch 9/10 copies collapsing into one of each, plus their helper packages going away.Why are these changes being made?
Testing instructions
npm run typecheckandnpm testpass.biome checkreports one pre-existing organizeImports finding insrc/react-scanner.d.ts, which this PR does not touch.