fix(deps): remediate vulnerable minimatch via typescript-eslint 8 - #53
Merged
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.
Dependabot cannot update the vulnerable transitive
minimatch@9.0.3because@typescript-eslint6.x pins that version. This migrates the TypeScript ESLint parser/plugin to v8 while keeping ESLint 8.57.x and the existing eslintrc configuration, avoiding the unrelated ESLint 10 / Node 20 migration in #40.The PR includes a temporary CI step to regenerate the lockfile and verify lint/tests. That temporary CI scaffolding will be removed before merge once the regenerated lockfile lands.