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 #558

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 29, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite (source) ^5.2.11 -> ^6.0.0 age adoption passing confidence

Release Notes

vitejs/vite (vite)

v6.1.0

Compare Source

v6.0.11

Compare Source

v6.0.10

Compare Source

v6.0.9

Compare Source

  • fix!: check host header to prevent DNS rebinding attacks and introduce server.allowedHosts (bd896fb)
  • fix!: default server.cors: false to disallow fetching from untrusted origins (b09572a)
  • fix: verify token for HMR WebSocket connection (029dcd6)

v6.0.8

Compare Source

v6.0.7

Compare Source

v6.0.6

Compare Source

v6.0.5

Compare Source

v6.0.4

Compare Source

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source


Configuration

📅 Schedule: 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.

Copy link
Contributor Author

renovate bot commented Nov 29, 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: frontend-service/package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @quasar/vite-plugin@1.7.0
npm error Found: vite@6.1.1
npm error node_modules/vite
npm error   dev vite@"^6.0.0" from the root project
npm error   peer vite@"^5.0.0 || ^6.0.0" from @vitejs/plugin-vue@5.2.1
npm error   node_modules/@vitejs/plugin-vue
npm error     dev @vitejs/plugin-vue@"^5.0.4" from the root project
npm error     peer @vitejs/plugin-vue@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from @quasar/vite-plugin@1.7.0
npm error     node_modules/@quasar/vite-plugin
npm error       dev @quasar/vite-plugin@"^1.7.0" from the root project
npm error   1 more (@vitejs/plugin-vue-jsx)
npm error
npm error Could not resolve dependency:
npm error peer vite@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from @quasar/vite-plugin@1.7.0
npm error node_modules/@quasar/vite-plugin
npm error   dev @quasar/vite-plugin@"^1.7.0" from the root project
npm error
npm error Conflicting peer dependency: vite@5.4.14
npm error node_modules/vite
npm error   peer vite@"^2.0.0 || ^3.0.0 || ^4.0.0 || ^5.0.0" from @quasar/vite-plugin@1.7.0
npm error   node_modules/@quasar/vite-plugin
npm error     dev @quasar/vite-plugin@"^1.7.0" 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-02-21T18_33_06_543Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-02-21T18_33_06_543Z-debug-0.log

@renovate renovate bot force-pushed the renovate/vite-6.x branch 13 times, most recently from a2b7f62 to 3d36525 Compare December 6, 2024 16:47
@renovate renovate bot force-pushed the renovate/vite-6.x branch 11 times, most recently from 9713eab to 6f0caea Compare December 11, 2024 15:08
@renovate renovate bot force-pushed the renovate/vite-6.x branch 4 times, most recently from 86bb094 to 9921ca4 Compare December 16, 2024 21:20
@renovate renovate bot force-pushed the renovate/vite-6.x branch 8 times, most recently from 3b54414 to c41ad6a Compare February 3, 2025 00:44
@renovate renovate bot force-pushed the renovate/vite-6.x branch 7 times, most recently from ea61ade to 1688330 Compare February 9, 2025 05:18
@renovate renovate bot force-pushed the renovate/vite-6.x branch 10 times, most recently from 1173147 to 497a2f3 Compare February 18, 2025 14:41
@renovate renovate bot force-pushed the renovate/vite-6.x branch 3 times, most recently from 3903a39 to a5425fd Compare February 20, 2025 02:19
@renovate renovate bot force-pushed the renovate/vite-6.x branch from a5425fd to 09e76f6 Compare February 21, 2025 18:33
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.

0 participants