chore(deps): upgrade vite to v6 [security]#88
Conversation
Upgrades vite from ^5.4.11 to ^6.0.0 (resolved to 6.4.2). Addresses multiple server.fs.deny CVEs: - CVE-2025-30208 (GHSA-x574-m823-4x7w) - bypass via ?raw?? suffix - CVE-2025-31125 (GHSA-4r4m-qw57-chr8) - bypass via ?inline&import - CVE-2025-31486 (GHSA-xcj6-pq6g-qj4x) - bypass via .svg or relative paths - CVE-2025-32395 (GHSA-356w-63v5-8wf4) - bypass via invalid request-target - CVE-2025-46565 (GHSA-859w-5945-r5v3) - bypass via /. for project root files Migration notes (v5 -> v6): - No Sass usage: modern API change is not applicable - No SSR: Environment API changes do not apply - No custom resolve.conditions: default change does not apply - Library mode CSS filename: package uses no CSS output so not applicable - All 69 tests pass, build output unchanged Closes #87 (original renovate PR had lock file conflicts)
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (2)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Summary
Upgrades
vitefrom^5.4.11→^6.0.0(resolved to 6.4.2).This supersedes #87 (renovate PR) which had an unresolvable lock file conflict and only bumped to
5.4.20in the lockfile despite claiming v6. This PR does the actual v6 upgrade with a clean lock file.Security CVEs Addressed
server.fs.denybypass via?raw??suffix?inline&import.svgor relative pathsrequest-target(#in URL)/.for files under project rootMigration Assessment (v5 → v6)
No migration changes required for this codebase. Here's the full audit:
resolve.conditionsdefault changedresolve.conditionsconfiguredstyle.css→<name>.css)fs.cachedChecksremoveddotenv-expandvariable orderjson.stringifynew default'auto'@rollup/plugin-commonjsstrictRequires: trueVerification
pnpm build- clean build, output size unchangedpnpm test- all 69 tests passgit diff --stat- onlypackage.json+pnpm-lock.yamlchanged (zero unintended changes)