Bump vite from 5.4.21 to 6.4.2

[dependabot]

Bumps vite from 5.4.21 to 6.4.2.

Release notes

Sourced from vite's releases.

v6.4.2

Please refer to CHANGELOG.md for details.

v6.4.1

Please refer to CHANGELOG.md for details.

v6.4.0

Please refer to CHANGELOG.md for details.

v6.3.7

Please refer to CHANGELOG.md for details.

v6.3.6

Please refer to CHANGELOG.md for details.

Changelog

Sourced from vite's changelog.

6.4.2 (2026-04-06)

• fix: apply server.fs check to env transport (#22159) (#22163) (fe28e47), closes #22159 #22163
• fix: avoid path traversal with optimize deps sourcemap handler (#22161) (ca4da5d), closes #22161

6.4.1 (2025-10-20)

• fix(dev): trim trailing slash before server.fs.deny check (#20968) (#20969) (1114b5d), closes #20968 #20969

6.4.0 (2025-10-15)

• feat: allow passing down resolved config to vite's createServer (#20932) (ca6455e), closes #20932

6.3.7 (2025-10-14)

• fix(esbuild): inject esbuild helpers correctly for esbuild 0.25.9+ (#20940) (c59a222), closes #20940

6.3.6 (2025-09-08)

• fix: apply fs.strict check to HTML files (#20736) (0ab19ea), closes #20736
• fix: upgrade sirv to 3.0.2 (#20735) (e11d240), closes #20735
• test: detect ts support via process.features (#20544) (7d99229), closes #20544

6.3.5 (2025-05-05)

• fix(ssr): handle uninitialized export access as undefined (#19959) (fd38d07), closes #19959

6.3.4 (2025-04-30)

• fix: check static serve file inside sirv (#19965) (c22c43d), closes #19965
• fix(optimizer): return plain object when using require to import externals in optimized dependenci (efc5eab), closes #19940
• refactor: remove duplicate plugin context type (#19935) (d6d01c2), closes #19935

6.3.3 (2025-04-24)

• fix: ignore malformed uris in tranform middleware (#19853) (e4d5201), closes #19853

... (truncated)

Commits

• 6b3fad0 release: v6.4.2
• ca4da5d fix: avoid path traversal with optimize deps sourcemap handler (#22161)
• fe28e47 fix: apply server.fs check to env transport (#22159) (#22163)
• 5487f4f release: v6.4.1
• 1114b5d fix(dev): trim trailing slash before server.fs.deny check (#20968) (#20969)
• f12697c release: v6.4.0
• ca6455e feat: allow passing down resolved config to vite's createServer (#20932)
• 0e173d8 release: v6.3.7
• c59a222 fix(esbuild): inject esbuild helpers correctly for esbuild 0.25.9+ (#20940)
• 3f337c5 release: v6.3.6
• Additional commits viewable in compare view

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 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.

[thewtex]

@hjmjohnson do you know why we get the error:

Error: Unable to resolve action insightsoftwareconsortium/itkapplyclangformataction@main, unable to find version main

It seems main is there?

[hjmjohnson]

@thewtex The action repo InsightSoftwareConsortium/ITKApplyClangFormatAction still uses master as its default branch, but apply-clang-format.yml references @main — so GitHub Actions can't resolve the ref.

(The other action, ITKClangFormatLinterAction, is fine — its default branch is already main.)

My preference is to fix this upstream in ITKApplyClangFormatAction rather than patching the workflow ref here:

1. Rename the default branch from master → main in ITKApplyClangFormatAction.
2. Create a master tag pinned to the final commit on the old branch, so any existing @master refs still resolve to the last known-good state rather than silently breaking.
3. Push a poison-pill commit to the (now non-default) master branch — e.g. a README.md that says "This branch is deprecated. Use main." plus a workflow that always fails with a clear message. That way anyone still referencing @master as a branch gets an immediate, obvious error instead of silently running stale code.

This keeps the migration clean and discoverable for all downstream consumers, not just ITKElastix.

[thewtex]

@hjmjohnson ok

Create a master tag

Did you mean "branch" instead of "tag"?

[hjmjohnson]

@hjmjohnson ok

Create a master tag

Did you mean "branch" instead of "tag"?

@thewtex

Either would work. I proposed using "tag" as the hash of the current master branch so it cannot be added to, and to avoid issues like "git push origin/master," which does not work with the tag. Or make master a protected branch. Either would work as long as both the master and the main are resolved to the correct content for backward compatibility.

tag <-- use unintended future behaviors as breaking
branch <-- allow master to float over time.

[thewtex]

That action was unused -- removing in #384