Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency @vue/eslint-config-typescript to v12 #458

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 29, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vue/eslint-config-typescript 4.0.0 -> 12.0.0 age adoption passing confidence

Release Notes

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

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:

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.

v9.1.0

Compare Source

  • feat: allow using const foo = require('foo') in plain CommonJS modules (109b3f8)

v9.0.1

Compare Source

  • Fixes the peer dependency version of eslint-plugin-vue (#​37) (@​2malh)

v9.0.0

Compare Source

  • Upgrade vue-eslint-parser to v8;
  • Drop support for Node.js < v12.22.0, v13, >=v14 < v14.17.0, v15

v8.0.0

Compare Source

Thanks to @​cexbrayat

v7.0.0

Compare Source

Update to @typescript-eslint/* v4.

See detailed breaking changes at https://github.com/typescript-eslint/typescript-eslint/releases/tag/v4.0.0

v6.0.0

Compare Source

Update to @​typescript-eslint/* v3. See detailed breaking changes at https://github.com/typescript-eslint/typescript-eslint/releases/tag/v3.0.0

The most notable ones are:

  • Dropped support for Node version 8
  • Dropped support for TypeScript 3.2

Check out the linked issues for more information about added/removed rules:

v5.1.0

Compare Source

Accept eslint@7 & eslint-plugin-vue@7 as peer dependencies

v5.0.2

Compare Source

Fix parser loading in Yarn 2 #​8

v5.0.1

Compare Source

Fix the Cannot read config file error for the recommended ruleset https://github.com/vuejs/eslint-config-typescript/pull/6

v5.0.0


Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" in timezone Europe/Stockholm, 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.

Copy link
Contributor Author

renovate bot commented Mar 3, 2024

Renovate Ignore Notification

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

@renovate renovate bot deleted the renovate/vue-eslint-config-typescript-12.x branch March 3, 2024 23:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant