fix(deps): update dependency vite to v6.4.1 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
vite (source)	6.4.0 -> 6.4.1
vite (source)	6.3.6 -> 6.4.1

GitHub Vulnerability Alerts

CVE-2025-62522

Summary

Files denied by server.fs.deny were sent if the URL ended with \ when the dev server is running on Windows.

Impact

Only apps that match the following conditions are affected:

• explicitly exposes the Vite dev server to the network (using --host or server.host config option)
• running the dev server on Windows

Details

server.fs.deny can contain patterns matching against files (by default it includes .env, .env.*, *.{crt,pem} as such patterns). These patterns were able to bypass by using a back slash(\). The root cause is that fs.readFile('/foo.png/') loads /foo.png.

PoC

npm create vite@latest
cd vite-project/
cat "secret" > .env
npm install
npm run dev
curl --request-target /.env\ http://localhost:5173

---

Release Notes

vitejs/vite (vite)

v6.4.1

Compare Source

Please refer to CHANGELOG.md for details.

---

Configuration

📅 Schedule: Branch creation - "" (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 these updates 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]

⚠️ 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: pnpm-lock.yaml

Scope: all 544 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 20, reused 0, downloaded 0, added 0
Progress: resolved 21, reused 0, downloaded 0, added 0
Progress: resolved 57, reused 0, downloaded 0, added 0
Progress: resolved 120, reused 0, downloaded 0, added 0
Progress: resolved 140, reused 0, downloaded 0, added 0
Progress: resolved 157, reused 0, downloaded 0, added 0
Progress: resolved 163, reused 0, downloaded 0, added 0
Progress: resolved 192, reused 0, downloaded 0, added 0
Progress: resolved 196, reused 0, downloaded 0, added 0
packages/integrations/sitemap            |  WARN  deprecated [email protected]
/tmp/renovate/repos/github/withastro/astro/packages/astro/test/fixtures/astro-info-versions:
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for [email protected] published by Sat Oct 18 2025 10:13:13 GMT+0000 (Coordinated Universal Time) while fetching it from https://registry.npmjs.org/. Version 6.4.1 satisfies the specs but was released at Mon Oct 20 2025 05:27:28 GMT+0000 (Coordinated Universal Time)

This error happened while installing a direct dependency of /tmp/renovate/repos/github/withastro/astro/packages/astro/test/fixtures/astro-info-versions

The latest release of vite is "7.1.11". Published at 10/20/2025

Other releases are:
  * alpha: 6.0.0-alpha.24 published at 9/4/2024
  * beta: 7.1.0-beta.1 published at 8/5/2025
  * previous: 5.4.21 published at 10/20/2025

If you need the full list of all 684 published versions run "$ pnpm view vite versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude
Progress: resolved 204, reused 0, downloaded 0, added 0

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3a5c811

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR