Skip to content

chore(deps): update dependency eslint-plugin-vue to v10#115

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-plugin-vue-10.x
Open

chore(deps): update dependency eslint-plugin-vue to v10#115
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-plugin-vue-10.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 19, 2025

This PR contains the following updates:

Package Change Age Confidence
eslint-plugin-vue (source) ^9.29.0^10.0.0 age confidence

Release Notes

vuejs/eslint-plugin-vue (eslint-plugin-vue)

v10.8.0

Compare Source

v10.7.0

Compare Source

Minor Changes
Patch Changes
  • Fixed false positives in vue/define-props-destructuring rule when imported types are passed to defineProps (#​2995)
  • Updated Vue 3 export names resources: added DirectiveModifiers (#​2996)
  • Updated Vue 3 export names resources: added nodeOps and patchProp (#​2986)

v10.6.2

Compare Source

Patch Changes

v10.6.1

Compare Source

Patch Changes

v10.6.0

Compare Source

Minor Changes
Patch Changes

v10.5.1

Compare Source

Patch Changes

v10.5.0

Compare Source

Minor Changes
Patch Changes

v10.4.0

Compare Source

Minor Changes
Patch Changes

v10.3.0

Compare Source

Minor Changes
Patch Changes

v10.2.0

Compare Source

Minor Changes
Patch Changes

v10.1.0

Compare Source

✨ Enhancements

Full Changelog: vuejs/eslint-plugin-vue@v10.0.1...v10.1.0

v10.0.1

Compare Source

🐛 Bug Fixes

⚙️ Updates

Full Changelog: vuejs/eslint-plugin-vue@v10.0.0...v10.0.1

v10.0.0

Compare Source

💥 Breaking changes

✨ Enhancements

⚙️ Updates

  • #​2171 Updated resources.
  • #​2675 Deprecated Vue 2 only rules. They will be removed in eslint-plugin-vue v11.

Full Changelog: vuejs/eslint-plugin-vue@v9.33.0...v10.0.0


Configuration

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

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

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 renovate bot force-pushed the renovate/eslint-plugin-vue-10.x branch 5 times, most recently from 3d983ed to cf3dc28 Compare December 23, 2025 09:47
@renovate renovate bot force-pushed the renovate/eslint-plugin-vue-10.x branch 2 times, most recently from be372e2 to 0b5d724 Compare January 19, 2026 09:27
@renovate renovate bot force-pushed the renovate/eslint-plugin-vue-10.x branch 3 times, most recently from 2620ba4 to 28d7a37 Compare January 28, 2026 10:45
@renovate renovate bot force-pushed the renovate/eslint-plugin-vue-10.x branch 3 times, most recently from b0c7eec to a8b823a Compare February 11, 2026 07:52
@renovate renovate bot force-pushed the renovate/eslint-plugin-vue-10.x branch from a8b823a to 745dfe6 Compare February 14, 2026 02:06
@renovate renovate bot force-pushed the renovate/eslint-plugin-vue-10.x branch 2 times, most recently from 1f646c0 to 1c68c7f Compare February 25, 2026 13:33
@renovate renovate bot force-pushed the renovate/eslint-plugin-vue-10.x branch from 1c68c7f to bec9181 Compare March 2, 2026 15:09
@renovate
Copy link
Contributor Author

renovate bot commented Mar 2, 2026

⚠️ 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/eslint-plugin@8.33.1
npm warn Found: typescript@5.9.3
npm warn node_modules/typescript
npm warn   dev typescript@"~5.9.0" from the root project
npm warn   7 more (@storybook/vue3-vite, @vue/eslint-config-typescript, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer typescript@">=4.8.4 <5.9.0" from @typescript-eslint/eslint-plugin@8.33.1
npm warn node_modules/@typescript-eslint/eslint-plugin
npm warn   @typescript-eslint/eslint-plugin@"8.33.1" from typescript-eslint@8.33.1
npm warn   node_modules/typescript-eslint
npm warn
npm warn Conflicting peer dependency: typescript@5.8.3
npm warn node_modules/typescript
npm warn   peer typescript@">=4.8.4 <5.9.0" from @typescript-eslint/eslint-plugin@8.33.1
npm warn   node_modules/@typescript-eslint/eslint-plugin
npm warn     @typescript-eslint/eslint-plugin@"8.33.1" from typescript-eslint@8.33.1
npm warn     node_modules/typescript-eslint
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/parser@8.33.1
npm error Found: typescript@5.9.3
npm error node_modules/typescript
npm error   dev typescript@"~5.9.0" from the root project
npm error   typescript@"^5.8.3" from @storybook/vue3-vite@9.0.5
npm error   node_modules/@storybook/vue3-vite
npm error     dev @storybook/vue3-vite@"^9.0.1" from the root project
npm error   6 more (@vue/eslint-config-typescript, @vue/language-core, ...)
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.8.4 <5.9.0" from @typescript-eslint/parser@8.33.1
npm error node_modules/@typescript-eslint/parser
npm error   peer @typescript-eslint/parser@"^8.33.1" from @typescript-eslint/eslint-plugin@8.33.1
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     @typescript-eslint/eslint-plugin@"8.33.1" from typescript-eslint@8.33.1
npm error     node_modules/typescript-eslint
npm error       typescript-eslint@"^8.26.0" from @vue/eslint-config-typescript@14.5.0
npm error       node_modules/@vue/eslint-config-typescript
npm error   @typescript-eslint/parser@"8.33.1" from typescript-eslint@8.33.1
npm error   node_modules/typescript-eslint
npm error     typescript-eslint@"^8.26.0" from @vue/eslint-config-typescript@14.5.0
npm error     node_modules/@vue/eslint-config-typescript
npm error       dev @vue/eslint-config-typescript@"^14.1.1" from the root project
npm error   1 more (eslint-plugin-vue)
npm error
npm error Conflicting peer dependency: typescript@5.8.3
npm error node_modules/typescript
npm error   peer typescript@">=4.8.4 <5.9.0" from @typescript-eslint/parser@8.33.1
npm error   node_modules/@typescript-eslint/parser
npm error     peer @typescript-eslint/parser@"^8.33.1" from @typescript-eslint/eslint-plugin@8.33.1
npm error     node_modules/@typescript-eslint/eslint-plugin
npm error       @typescript-eslint/eslint-plugin@"8.33.1" from typescript-eslint@8.33.1
npm error       node_modules/typescript-eslint
npm error         typescript-eslint@"^8.26.0" from @vue/eslint-config-typescript@14.5.0
npm error         node_modules/@vue/eslint-config-typescript
npm error     @typescript-eslint/parser@"8.33.1" from typescript-eslint@8.33.1
npm error     node_modules/typescript-eslint
npm error       typescript-eslint@"^8.26.0" from @vue/eslint-config-typescript@14.5.0
npm error       node_modules/@vue/eslint-config-typescript
npm error         dev @vue/eslint-config-typescript@"^14.1.1" from the root project
npm error     1 more (eslint-plugin-vue)
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/2026-03-02T15_08_57_313Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-02T15_08_57_313Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants