Skip to content

Bump vite from 5.4.11 to 5.4.14#42

Merged
cawalch merged 1 commit intomainfrom
dependabot/npm_and_yarn/vite-5.4.14
Jan 31, 2025
Merged

Bump vite from 5.4.11 to 5.4.14#42
cawalch merged 1 commit intomainfrom
dependabot/npm_and_yarn/vite-5.4.14

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot bot commented on behalf of github Jan 22, 2025

Bumps vite from 5.4.11 to 5.4.14.

Release notes

Sourced from vite's releases.

v5.4.14

Please refer to CHANGELOG.md for details.

v5.4.13

Please refer to CHANGELOG.md for details.

v5.4.12

This version contains a breaking change due to security fixes. See GHSA-vg6x-rcgg-rjx6 for more details.

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

5.4.14 (2025-01-21)

5.4.13 (2025-01-20)

5.4.12 (2025-01-20)

  • fix!: check host header to prevent DNS rebinding attacks and introduce server.allowedHosts (9da4abc)
  • fix!: default server.cors: false to disallow fetching from untrusted origins (dfea38f)
  • fix: verify token for HMR WebSocket connection (b71a5c8)
  • chore: add deps update changelog (ecd2375)
Commits
  • e7eb3c5 release: v5.4.14
  • 7d1699c fix: allow CORS from loopback addresses by default (#19249)
  • 9df6e6b fix: preview.allowedHosts with specific values was not respected (#19246)
  • a1824c5 release: v5.4.13
  • 5946215 fix: try parse server.origin URL (#19241)
  • f428aa9 release: v5.4.12
  • 9da4abc fix!: check host header to prevent DNS rebinding attacks and introduce `serve...
  • b71a5c8 fix: verify token for HMR WebSocket connection
  • dfea38f fix!: default server.cors: false to disallow fetching from untrusted origins
  • ecd2375 chore: add deps update changelog
  • See full diff in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 22, 2025
@cawalch
Copy link
Copy Markdown
Collaborator

cawalch commented Jan 22, 2025

needs a crypto.getRandomValues polyfill for node 16

@springcomp
Copy link
Copy Markdown
Contributor

springcomp commented Jan 23, 2025

Should we bother supporting node 16 ?
I mean, we should strive to have wide compatibility, but that should be traded off with the "cost" of maintaining compatibilty.
Also, where do we use random values in JmesPath 🤔 ?

@cawalch
Copy link
Copy Markdown
Collaborator

cawalch commented Jan 29, 2025

Should we bother supporting node 16 ? I mean, we should strive to have wide compatibility, but that should be traded off with the "cost" of maintaining compatibilty.

I don't think it's worth maintaining compatibility since node 16 went EoL over 1 year and 4 months ago. Plenty of other widely used packages have since dropped support for it too.

https://nodejs.org/en/blog/announcements/nodejs16-eol

Also, where do we use random values in JmesPath 🤔 ?

Looks like it comes from vitest--the testing framework.

@springcomp
Copy link
Copy Markdown
Contributor

Looks like [random usage] comes from vitest--the testing framework.

In that case, that would be a dev dependency.
I’m happy with whatever decision you take.

OK to drop support for EOLed versions.

@cawalch
Copy link
Copy Markdown
Collaborator

cawalch commented Jan 31, 2025

@dependabot rebase

Bumps [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite) from 5.4.11 to 5.4.14.
- [Release notes](https://github.com/vitejs/vite/releases)
- [Changelog](https://github.com/vitejs/vite/blob/v5.4.14/packages/vite/CHANGELOG.md)
- [Commits](https://github.com/vitejs/vite/commits/v5.4.14/packages/vite)

---
updated-dependencies:
- dependency-name: vite
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/vite-5.4.14 branch from ff5f3fd to 6194b85 Compare January 31, 2025 20:31
@cawalch cawalch merged commit 0829010 into main Jan 31, 2025
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/vite-5.4.14 branch January 31, 2025 20:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants