Update dependency eslint to v9 (1.10)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint (source)	8.57.0 -> 9.4.0

---

Release Notes

eslint/eslint (eslint)

v9.4.0

Compare Source

v9.3.0

Compare Source

v9.2.0

Compare Source

v9.1.1

Compare Source

v9.1.0

Compare Source

v9.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "after 11pm on friday,before 7am on saturday" in timezone Etc/Greenwich, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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 has been generated by Mend Renovate. View repository job log here.

[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 ERESOLVE overriding peer dependency
npm warn While resolving: @typescript-eslint/utils@6.21.0
npm warn Found: eslint@9.4.0
npm warn node_modules/eslint
npm warn   dev eslint@"9.4.0" from the root project
npm warn   16 more (@babel/eslint-parser, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer eslint@"^7.0.0 || ^8.0.0" from @typescript-eslint/utils@6.21.0
npm warn node_modules/@typescript-eslint/utils
npm warn   @typescript-eslint/utils@"^6.0.0 || ^7.0.0" from eslint-plugin-jest@28.5.0
npm warn   node_modules/eslint-plugin-jest
npm warn
npm warn Conflicting peer dependency: eslint@8.57.0
npm warn node_modules/eslint
npm warn   peer eslint@"^7.0.0 || ^8.0.0" from @typescript-eslint/utils@6.21.0
npm warn   node_modules/@typescript-eslint/utils
npm warn     @typescript-eslint/utils@"^6.0.0 || ^7.0.0" from eslint-plugin-jest@28.5.0
npm warn     node_modules/eslint-plugin-jest
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-airbnb-base@15.0.0
npm error Found: eslint@9.4.0
npm error node_modules/eslint
npm error   dev eslint@"9.4.0" from the root project
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/eslint-parser@7.24.6
npm error   node_modules/@babel/eslint-parser
npm error     dev @babel/eslint-parser@"7.24.6" from the root project
npm error   15 more (@eslint-community/eslint-plugin-eslint-comments, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from eslint-config-airbnb-base@15.0.0
npm error node_modules/eslint-config-airbnb-base
npm error   dev eslint-config-airbnb-base@"15.0.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.0
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from eslint-config-airbnb-base@15.0.0
npm error   node_modules/eslint-config-airbnb-base
npm error     dev eslint-config-airbnb-base@"15.0.0" 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 /tmp/renovate/cache/others/npm/_logs/2024-05-31T22_30_45_487Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-31T22_30_45_487Z-debug-0.log

[ehuelsmann]

Impact of moving to ESLint v9 is way too big to accept on this maintenance branch.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 9.x releases. But if you manually upgrade to 9.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.