Skip to content

chore: bump eslint to 10.15 and typescript-eslint to 8.73, refresh lock - #2278

Open
cdietrich wants to merge 2 commits into
mainfrom
chore/bump-eslint-audit
Open

cdietrich wants to merge 2 commits into
mainfrom
chore/bump-eslint-audit

Conversation

@cdietrich

Copy link
Copy Markdown
Contributor

Bumps the lint tooling and refreshes the lockfile to reduce npm audit findings.

  • 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.
  • Lock refresh picks up patch releases (vite 8.3.8, rolldown 1.2.19, yeoman-generator 10.3.1, @npmcli/*).

npm audit goes from 42 to 41 findings.

Remaining findings

  • picomatch (GHSA-fc5q-39xc-vjpf): there is no patched release yet (all versions up to 4.0.7 are affected); several fix PRs are open upstream.
  • minimatch < 11.0.1: there is no fix on the 10.x line. vscode-languageclient, typedoc, @vscode/vsce, and the yeoman packages still require minimatch ^10. Overriding to 11 is not an option because minimatch 11 removes makeRe() and matchOne(), which vscode-languageclient and typedoc call. The next prerelease of vsce already uses ^11.

The published langium package is not affected by either advisory.

Verification

npm run build, npm run lint, and npm test pass locally.

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

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant