Skip to content

chore(deps): update dependency @vitejs/plugin-vue to v6#188

Closed
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/vitejs-plugin-vue-6.x
Closed

chore(deps): update dependency @vitejs/plugin-vue to v6#188
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/vitejs-plugin-vue-6.x

Conversation

@renovate

@renovate renovate Bot commented Jul 1, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@vitejs/plugin-vue (source) ^5.2.1 -> ^6.0.0 age confidence

Release Notes

vitejs/vite-plugin-vue (@​vitejs/plugin-vue)

v6.0.1

Bug Fixes
Performance Improvements
Miscellaneous Chores
Build System

v6.0.0

Bug Fixes
Miscellaneous Chores
Code Refactoring

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), 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.

@renovate renovate Bot added the dependencies label Jul 1, 2025
@renovate

renovate Bot commented Jul 1, 2025

Copy link
Copy Markdown
Contributor Author

⚠️ 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: frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @quasar/vite-plugin@1.9.0
npm error Found: @vitejs/plugin-vue@6.0.1
npm error node_modules/@vitejs/plugin-vue
npm error   dev @vitejs/plugin-vue@"^6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @vitejs/plugin-vue@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from @quasar/vite-plugin@1.9.0
npm error node_modules/@quasar/vite-plugin
npm error   dev @quasar/vite-plugin@"^1.8.1" from the root project
npm error
npm error Conflicting peer dependency: @vitejs/plugin-vue@5.2.4
npm error node_modules/@vitejs/plugin-vue
npm error   peer @vitejs/plugin-vue@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from @quasar/vite-plugin@1.9.0
npm error   node_modules/@quasar/vite-plugin
npm error     dev @quasar/vite-plugin@"^1.8.1" 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 /runner/cache/others/npm/_logs/2025-08-07T00_04_20_917Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-08-07T00_04_20_917Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/vitejs-plugin-vue-6.x branch from bc43077 to 7ae66cf Compare August 7, 2025 00:04
@g3force g3force closed this Aug 7, 2025
@g3force g3force deleted the renovate/vitejs-plugin-vue-6.x branch August 7, 2025 05:35
@renovate

renovate Bot commented Aug 7, 2025

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

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

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