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 vite to v6 #88

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 1, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) 4.5.5 -> 6.0.1 age adoption passing confidence

Release Notes

vitejs/vite (vite)

v6.0.1

Compare Source

v6.0.0

Compare Source

v5.4.11

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.10

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.9

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.8

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.7

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.6

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.5

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.4

Compare Source

Please refer to CHANGELOG.md for details.

v5.4.3

Compare Source

Copy link
Contributor Author

renovate bot commented Dec 1, 2024

⚠️ 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 error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @sveltejs/[email protected]
npm error Found: [email protected]
npm error node_modules/vite
npm error   dev vite@"6.0.1" from the root project
npm error   peer vite@">=3.x" from @poppanator/[email protected]
npm error   node_modules/@poppanator/sveltekit-svg
npm error     dev @poppanator/sveltekit-svg@"3.0.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^4.0.0" from @sveltejs/[email protected]
npm error node_modules/@sveltejs/kit
npm error   dev @sveltejs/kit@"1.27.2" from the root project
npm error   peer @sveltejs/kit@"^1.5.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/adapter-vercel
npm error     dev @sveltejs/adapter-vercel@"3.0.3" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vite
npm error   peer vite@"^4.0.0" from @sveltejs/[email protected]
npm error   node_modules/@sveltejs/kit
npm error     dev @sveltejs/kit@"1.27.2" from the root project
npm error     peer @sveltejs/kit@"^1.5.0" from @sveltejs/[email protected]
npm error     node_modules/@sveltejs/adapter-vercel
npm error       dev @sveltejs/adapter-vercel@"3.0.3" 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 /tmp/renovate/cache/others/npm/_logs/2024-12-01T10_31_42_457Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-01T10_31_42_457Z-debug-0.log

Copy link

vercel bot commented Dec 1, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
privacy-protect-68pv ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 1, 2024 10:32am

Copy link
Contributor Author

renovate bot commented Dec 1, 2024

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.

@renovate renovate bot deleted the renovate/vite-6.x branch December 1, 2024 13:47
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