Skip to content

chore(deps): update dependency vite to v8#221

Closed
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-vite
Closed

chore(deps): update dependency vite to v8#221
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-vite

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Mar 16, 2026

This PR contains the following updates:

Package Change Age Confidence
vite (source) ^7.3.1^8.0.0 age confidence

Release Notes

vitejs/vite (vite)

v8.0.0

Compare Source

Features
Bug Fixes

Configuration

📅 Schedule: Branch creation - "before 9am on monday" (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
Copy link
Contributor Author

renovate bot commented Mar 16, 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.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: unplugin-fonts@1.4.0
npm error Found: vite@8.0.0
npm error node_modules/vite
npm error   dev vite@"^8.0.0" from the root project
npm error   peer vite@"^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0" from @vitejs/plugin-vue@6.0.5
npm error   node_modules/@vitejs/plugin-vue
npm error     dev @vitejs/plugin-vue@"^6.0.4" from the root project
npm error   1 more (vite-plugin-vuetify)
npm error
npm error Could not resolve dependency:
npm error peer vite@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from unplugin-fonts@1.4.0
npm error node_modules/unplugin-fonts
npm error   dev unplugin-fonts@"^1.1.1" from the root project
npm error
npm error Conflicting peer dependency: vite@7.3.1
npm error node_modules/vite
npm error   peer vite@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0" from unplugin-fonts@1.4.0
npm error   node_modules/unplugin-fonts
npm error     dev unplugin-fonts@"^1.1.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/2026-03-16T01_11_28_830Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-03-16T01_11_28_830Z-debug-0.log

@v-kessler v-kessler closed this Mar 16, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Mar 16, 2026

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 8.x releases. But if you manually upgrade to 8.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/major-vite branch March 16, 2026 14:09
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.

1 participant