fix: update minimatch lockfile (9.0.5 -> 9.0.9) to resolve security alert#184
Merged
fix: update minimatch lockfile (9.0.5 -> 9.0.9) to resolve security alert#184
Conversation
marc0der
approved these changes
Mar 3, 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
1 participant
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.
Dependabot flagged a security vulnerability in
minimatchrequiring ≥9.0.7, but could not update it automatically because the lockfile was stale.minimatchis a transitive dependency of@trivago/prettier-plugin-sort-imports, which allows^9.0.0— so 9.0.9 is valid within its constraints. Runningnpm update minimatchupdates the nested lockfile entry from 9.0.5 → 9.0.9.Change: 4 lines in
package-lock.jsononly. No direct dependencies changed.Closes the Dependabot security alert for minimatch.