chore(deps): update dependency eslint-plugin-cypress to v4 (main)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-cypress	^3.6.0 -> ^4.1.0

---

Release Notes

cypress-io/eslint-plugin-cypress (eslint-plugin-cypress)

v4.1.0

Compare Source

v4.0.0

Compare Source

Features

• minimum version eslint v9 (b50181a)

BREAKING CHANGES

• Support ESLint v9 and above only

Support for ESlint v7 & v8 is removed
languageOptions ecmaVersion: 2019 and sourceType: module are removed from eslint-plugin-cypress/flat config
globals is updated to 15.11.0
eslint-plugin-n is updated to 17.11.1

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Europe/Berlin, 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 was generated by Mend Renovate. View the repository job log.

[max-nextcloud]

requires eslint 9 which we currently do not support.

[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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.5.0 || ^8.0.0" from @babel/[email protected]
npm error   node_modules/@babel/eslint-parser
npm error     peer @babel/eslint-parser@"^7.16.5" from @nextcloud/[email protected]
npm error     node_modules/@nextcloud/eslint-config
npm error       dev @nextcloud/eslint-config@"^8.4.1" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/[email protected]
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"7.9.0" from @typescript-eslint/[email protected]
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         @typescript-eslint/eslint-plugin@"^7.1.1" from @vue/[email protected]
npm error         node_modules/@vue/eslint-config-typescript
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error     2 more (eslint-plugin-es-x, eslint-plugin-n)
npm error   18 more (@nextcloud/eslint-config, @nextcloud/eslint-plugin, ...)
npm error
npm error Could not resolve dependency:
npm error dev eslint-plugin-cypress@"^4.1.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/eslint
npm error   peer eslint@">=9" from [email protected]
npm error   node_modules/eslint-plugin-cypress
npm error     dev eslint-plugin-cypress@"^4.1.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-10-30T15_59_15_142Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-10-30T15_59_15_142Z-debug-0.log

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.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.