fix(ci): resolve minimatch audit vulnerability#51
Merged
Conversation
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.
User description
Summary
overridesforminimatch,brace-expansion, andbalanced-matchto eliminate vulnerable minimatch chains in lint transitive dependenciespackage-lock.jsonso all minimatch consumers resolve tominimatch@10.2.1Why
CI run #22275799774 fails in
Dependency AuditonGHSA-3ppc-4f35-3m26(minimatch <10.2.1).Validation
npm ls minimatch --package-lock-onlyminimatch@10.2.1Generated description
Below is a concise technical summary of the changes proposed in this PR:
Resolves a security vulnerability in the
minimatchdependency by enforcing specific versions through npm overrides. Ensures CI stability by migrating to HTTPS tarball sources, removing the need for SSH keys during dependency installation.Latest Contributors(2)