🚨 [security] Update vite 6.2.0 → 6.2.3 (patch) #356
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ vite (6.2.0 → 6.2.3) · Repo · Changelog
Security Advisories 🚨
🚨 Vite bypasses server.fs.deny when using ?raw??
Release Notes
6.2.3
6.2.2
6.2.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 46 commits:
release: v6.2.3fix: fs raw query with query separators (#19702)release: v6.2.2docs: add vscode debug error situation description (#19631)fix(preview): use preview https config, not server (#19633)fix: await client buildStart on top level buildStart (#19624)fix(indexHtml): ensure correct URL when querying module graph (#19601)feat: show friendly error for malformed `base` (#19616)fix(ssr): use optional chaining to prevent "undefined is not an object" happening in `ssrRewriteStacktrace` (#19612)fix(deps): update all non-major dependencies (#19613)fix(css): inline css correctly for double quote use strict (#19590)feat(worker): show asset filename conflict warning (#19591)chore: extend commit hash correctly when ambigious with a non-commit object (#19600)docs(troubleshooting): mention devcontainers as culprit for hanging requests (#19599)release: v6.2.1refactor: use `applyToEnvironment` in internal plugins (#19588)fix(sourcemap): combine sourcemaps with multiple sources without matched source (#18971)refactor: remove `isBuild` check from preAliasPlugin (#19587)docs: clarify `build.manifest` / `build.ssrManifest` option values (#19582)refactor: restore endsWith usage (#19554)feat: add `*?url&no-inline` type and warning for `.json?inline` / `.json?no-inline` (#19566)test: convert config playground to unit tests (#19568)test: convert resolve-config playground to unit tests (#19567)fix(reporter): fix incorrect bundle size calculation with non-ASCII characters (#19561)perf: flush compile cache after 10s (#19537)ci: update feature template label to `pending triage` (#19553)fix(deps): update all non-major dependencies (#19555)chore(deps): update dependency globals to v16 (#19556)fix(ssr): named export should overwrite export all (#19534)docs: remove $ prefix from create-vite terminal commands in README (#19532)fix(css): stabilize css module hashes with lightningcss in dev mode (#19481)ci: bug/feature template add type key (#19550)release: [email protected]chore(css): move environment destructuring after condition check (#19492)chore(html): remove unnecessary value check (#19491)fix(create-vite): make custom command visible (#19519)docs(create-vite): recommend eslint-react for linting (#19524)docs: make `import.meta.glob` example code more accurate (#19526)docs: fix pnpm version in contributing guide (#19515)fix(create-vite): remove eslint-plugin-react (#19514)test: add glob import test case (#19516)chore: remove prompts alias (#19507)release: [email protected]feat(create-vite): use `@clack/prompts` (#19445)release: [email protected]release: [email protected]Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands