Repository navigation
Conversation
eslint 10.15 and typescript-eslint 8.73 depend on minimatch ^11, which is not affected by GHSA-g3hv-75wg-m249. The lock refresh picks up patch releases (vite 8.3.8, rolldown 1.2.19, yeoman-generator 10.3.1, npmcli).
This branch has not been deployed
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.
Bumps the lint tooling and refreshes the lockfile to reduce
npm auditfindings.eslint~10.14.0 → ~10.15.0 and@typescript-eslint/*~8.72.1 → ~8.73.0. Both now depend on minimatch ^11, which is not affected by GHSA-g3hv-75wg-m249.npm auditgoes from 42 to 41 findings.Remaining findings
vscode-languageclient,typedoc,@vscode/vsce, and the yeoman packages still require minimatch ^10. Overriding to 11 is not an option because minimatch 11 removesmakeRe()andmatchOne(), which vscode-languageclient and typedoc call. Thenextprerelease of vsce already uses ^11.The published
langiumpackage is not affected by either advisory.Verification
npm run build,npm run lint, andnpm testpass locally.