chore(deps): update dependency typescript-eslint to v8.46.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
typescript-eslint (source)	8.45.0 -> 8.46.0

---

Release Notes

typescript-eslint/typescript-eslint (typescript-eslint)

v8.46.0

Compare Source

🚀 Features

• typescript-eslint: export util types (#​10848, #​10849)

❤️ Thank You

• Mister-Hope @​Mister-Hope

You can read about our versioning strategy and releases on our website.

v8.45.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.44.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.44.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.43.0

Compare Source

🩹 Fixes

• eslint-plugin: [no-deprecated] should report deprecated exports and reexports (#​11359)

❤️ Thank You

• Victor Genaev @​mainframev

You can read about our versioning strategy and releases on our website.

v8.42.0

Compare Source

🚀 Features

• deprecate tseslint.config() (#​11531)

🩹 Fixes

• typescript-eslint: handle non-normalized windows paths produced by jiti (#​11546)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

v8.41.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.40.0

Compare Source

🩹 Fixes

• typescript-eslint: export plugin, parser, and configs that are compatible with both defineConfig() and tseslint.config() (#​11475)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

v8.39.1

Compare Source

🩹 Fixes

• typescript-eslint: handle file:// urls in stack trace when inferring tsconfigRootDir (#​11464)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

v8.39.0

Compare Source

🚀 Features

• update to TypeScript 5.9.2 (#​11445)

❤️ Thank You

• Brad Zacher @​bradzacher

You can read about our versioning strategy and releases on our website.

v8.38.0

Compare Source

🩹 Fixes

• typescript-eslint: error on nested extends in tseslint.config() (#​11361)
• typescript-eslint: infer tsconfigRootDir with v8 API (#​11412)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

v8.37.0

Compare Source

🚀 Features

• typescript-estree: infer tsconfigRootDir from call stack (#​11370)

❤️ Thank You

• Josh Goldberg ✨

You can read about our versioning strategy and releases on our website.

v8.36.0

Compare Source

🚀 Features

• typescript-eslint: support basePath in tseslint.config() (#​11357)

❤️ Thank You

• Kirk Waiblinger @​kirkwaiblinger

You can read about our versioning strategy and releases on our website.

v8.35.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.35.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.34.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.34.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.33.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.33.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

v8.32.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

You can read about our versioning strategy and releases on our website.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ 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: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @types/[email protected]
npm error Found: @types/[email protected]
npm error node_modules/@types/chai
npm error   dev @types/chai@"5.2.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @types/chai@"<5.2.0" from @types/[email protected]
npm error node_modules/@types/chai-subset
npm error   dev @types/chai-subset@"1.3.6" from the root project
npm error
npm error Conflicting peer dependency: @types/[email protected]
npm error node_modules/@types/chai
npm error   peer @types/chai@"<5.2.0" from @types/[email protected]
npm error   node_modules/@types/chai-subset
npm error     dev @types/chai-subset@"1.3.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-10-08T22_45_46_026Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-08T22_45_46_026Z-debug-0.log