Thanks for the PR, @renovate[bot]!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	0da41d1
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/672e61b2b42d330008c9bd90
😎 Deploy Preview	https://deploy-preview-10309--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (🟢 up 8 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 0da41d1. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

Sent with 💌 from NxCloud.

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock

node:fs:1363
  const result = binding.mkdir(
                         ^

Error: ENOENT: no such file or directory, mkdir '/home/ubuntu/.cache/node/corepack/v1'
    at mkdirSync (node:fs:1363:26)
    at getTemporaryFolder (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21486:27)
    at download (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21760:21)
    at installVersion (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:21854:61)
    at async Engine.ensurePackageManager (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:22310:32)
    at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:22410:25)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.29.4/22.11.0/node_modules/corepack/dist/lib/corepack.cjs:23096:5) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'mkdir',
  path: '/home/ubuntu/.cache/node/corepack/v1'
}

Node.js v22.11.0

This doesn't make #10322 worse, so merging as-is. Heh.