chore(deps): update dependency @vue/eslint-config-typescript to v13

[descope]

This PR contains the following updates:

Package	Type	Update	Change
@vue/eslint-config-typescript	devDependencies	major	^9.1.0 -> ^13.0.0

---

Release Notes

vuejs/eslint-config-typescript (@​vue/eslint-config-typescript)

v13.0.0

Compare Source

Notable Changes

typescript-eslint is upgraded to v7.x. The full release notes can be found in their release blog: https://typescript-eslint.io/blog/announcing-typescript-eslint-v7

It's a small major release that only updates some peer dependency version requirements:

• Requires Node.js >= 18.18, TypeScript >= 4.7.4, ESLint >= 8.56

v12.0.0

Compare Source

Notable Changes

typescript-eslint is upgraded to v6.x. The full release notes can be found in their release blog: https://typescript-eslint.io/blog/announcing-typescript-eslint-v6/
Here are some notable changes you might encounter when upgrading @vue/eslint-config-typescript from v11 to v12:

• Requires Node.js >= 16, TypeScript >= 4.2.4, ESLint >= 7
• The default config:
  • valid-typeof rule is re-enabled because it's not always covered by TypeScript
• The recommended config:
  • No longer includes stylistic rules; because the upstream @typescript-eslint/eslint-plugin has split them into standalone configs.
  • Some rules' severity levels are changed from warn to error, such as @typescript-eslint/no-unused-vars.
  • A more complete list of changes can be found at https://github.com/typescript-eslint/typescript-eslint/discussions/6014

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

v11.0.0

Compare Source

Breaking Changes

• Bump eslint-plugin-vue to v9
• Drop Node.js v12 support

Other Notable Changes

• Use multiple parsers for more precise checking, and potentially improves performance (8c3628c)

v10.0.0

Compare Source

Breaking Change

• @typescript-eslint/* becomes dependencies instead of peer dependencies. It's because we now recommend using this package along with @rushstack/eslint-patch.

---

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,every weekend,before 5am every weekday" in timezone Asia/Jerusalem, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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 Renovate Bot.

[descope]

⚠ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @descope/vue-sdk@2.0.19
npm ERR! Found: eslint@7.32.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^7.32.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^8.56.0" from @vue/eslint-config-typescript@13.0.0
npm ERR! node_modules/@vue/eslint-config-typescript
npm ERR!   dev @vue/eslint-config-typescript@"^13.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-06-09T09_56_26_746Z-debug-0.log