Skip to content

chore(deps): update vue monorepo to v3.5.35#1077

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vue-monorepo
Open

chore(deps): update vue monorepo to v3.5.35#1077
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vue-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 15, 2026

This PR contains the following updates:

Package Change Age Confidence
vue (source) 3.5.323.5.35 age confidence

Release Notes

vuejs/core (vue)

v3.5.35

Compare Source

Bug Fixes
Performance Improvements

v3.5.34

Compare Source

Bug Fixes

v3.5.33

Compare Source

Bug Fixes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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 added the Renovate label May 15, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 18, 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 Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn idealTree Removing peerDependencies.vue in favor of dependencies.vue
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vue/server-renderer@3.5.32
npm error Found: vue@3.5.35
npm error node_modules/vue
npm error   vue@"3.5.35" from the root project
npm error   peer vue@"^3.2.25" from @vitejs/plugin-vue@6.0.7
npm error   node_modules/@vitejs/plugin-vue
npm error     dev @vitejs/plugin-vue@"6.0.7" from the root project
npm error   7 more (@vue/test-utils, @vue/tsconfig, @vueuse/core, ...)
npm error
npm error Could not resolve dependency:
npm error peer vue@"3.5.32" from @vue/server-renderer@3.5.32
npm error node_modules/@vue/server-renderer
npm error   peerOptional @vue/server-renderer@"3.x" from @vue/test-utils@2.4.10
npm error   node_modules/@vue/test-utils
npm error     dev @vue/test-utils@"2.4.10" from the root project
npm error
npm error Conflicting peer dependency: vue@3.5.32
npm error node_modules/vue
npm error   peer vue@"3.5.32" from @vue/server-renderer@3.5.32
npm error   node_modules/@vue/server-renderer
npm error     peerOptional @vue/server-renderer@"3.x" from @vue/test-utils@2.4.10
npm error     node_modules/@vue/test-utils
npm error       dev @vue/test-utils@"2.4.10" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-06-04T13_46_48_368Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-04T13_46_48_368Z-debug-0.log

@renovate renovate Bot changed the title chore(deps): update dependency vue to v3.5.34 chore(deps): update dependency vue to v3.5.35 May 27, 2026
@renovate renovate Bot changed the title chore(deps): update dependency vue to v3.5.35 chore(deps): update vue monorepo to v3.5.35 Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants