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.0.11 #2473

Merged
merged 1 commit into from
Jan 21, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 20, 2025

This PR contains the following updates:

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

Release Notes

vitejs/vite (vite)

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


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 changed the title chore(deps): update dependency vite to v6.0.8 chore(deps): update dependency vite to v6.0.9 Jan 20, 2025
@renovate renovate bot force-pushed the renovate/vite-6.x-lockfile branch 2 times, most recently from c3f206d to 1ae25c1 Compare January 20, 2025 17:13
@jobara
Copy link
Collaborator

jobara commented Jan 20, 2025

In Vite v6.0.9 introduced breaking changes related to a security fixes. This is causing an error with the laravel-vite-plugin ( laravel/vite-plugin#316 ). There is a workaround for setting the server config in the vite config file. However, I'm not sure if that's the best/recommended approach yet. Holding off updating this for the time being until there is more info/clarity of what to do. Perhaps a fix from laravel-vite-plugin will be released to fix the issue itself.

@renovate renovate bot changed the title chore(deps): update dependency vite to v6.0.9 chore(deps): update dependency vite to v6.0.10 Jan 21, 2025
@renovate renovate bot force-pushed the renovate/vite-6.x-lockfile branch from 1ae25c1 to f4262f4 Compare January 21, 2025 09:55
@renovate renovate bot changed the title chore(deps): update dependency vite to v6.0.10 chore(deps): update dependency vite to v6.0.11 Jan 21, 2025
@renovate renovate bot force-pushed the renovate/vite-6.x-lockfile branch from f4262f4 to cc343cc Compare January 21, 2025 13:03
@jobara jobara enabled auto-merge (squash) January 21, 2025 13:30
@jobara jobara merged commit cfd0cee into dev Jan 21, 2025
7 checks passed
@jobara jobara deleted the renovate/vite-6.x-lockfile branch January 21, 2025 13:31
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