feat(deps): upgrade upstream dependencies

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_browser_types/package.json

@@ -5,7 +5,7 @@
   "packageManager": "pnpm@11.24.0",
   "devDependencies": {
     "vite-plus": "latest",
-    "@vitest/browser-playwright": "5.0.4",
+    "@vitest/browser-playwright": "5.0.5",
     "playwright": "1.57.0",
     "typescript": "7.0.2"
   }

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_coverage/package.json

@@ -4,7 +4,7 @@
   "type": "module",
   "devDependencies": {
     "vite-plus": "latest",
-    "@vitest/coverage-v8": "5.0.4",
-    "@vitest/coverage-istanbul": "5.0.4"
+    "@vitest/coverage-v8": "5.0.5",
+    "@vitest/coverage-istanbul": "5.0.5"
   }
 }

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_install_managers/package.json

@@ -2,5 +2,5 @@
   "name": "test-v5-install-managers",
   "private": true,
   "type": "module",
-  "devDependencies": { "vite-plus": "latest", "vitest": "5.0.4" }
+  "devDependencies": { "vite-plus": "latest", "vitest": "5.0.5" }
 }

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_install_managers/snapshots.toml

@@ -8,8 +8,8 @@ steps = [
   { argv = ["vpt", "json-edit", "package.json", "packageManager", "npm@10.9.4"], snapshot = false },
   # Match the bundled runner throughout npm's peer graph. Otherwise newer
   # Vitest patches reached through optional peers can crash npm 10's resolver.
-  { argv = ["vpt", "json-edit", "package.json", "overrides.vitest", "5.0.4"], snapshot = false },
-  { argv = ["vpt", "json-edit", "package.json", "overrides.@vitest/browser", "5.0.4"], snapshot = false },
+  { argv = ["vpt", "json-edit", "package.json", "overrides.vitest", "5.0.5"], snapshot = false },
+  { argv = ["vpt", "json-edit", "package.json", "overrides.@vitest/browser", "5.0.5"], snapshot = false },
   { argv = ["vp", "install", "--ignore-scripts", "--", "--no-audit", "--no-fund"], snapshot = false, timeout = 180000 },
   ["vp", "test", "run"],
 ]

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_install_managers/snapshots/npm_install_and_runtime.md

@@ -3,10 +3,10 @@
 ## `vpt json-edit package.json packageManager npm@10.9.4`
 
 
-## `vpt json-edit package.json overrides.vitest 5.0.4`
+## `vpt json-edit package.json overrides.vitest 5.0.5`
 
 
-## `vpt json-edit package.json overrides.@vitest/browser 5.0.4`
+## `vpt json-edit package.json overrides.@vitest/browser 5.0.5`
 
 
 ## `vp install --ignore-scripts -- --no-audit --no-fund`

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_optional_packages/package.json

@@ -4,7 +4,7 @@
   "type": "module",
   "devDependencies": {
     "vite-plus": "latest",
-    "@vitest/ui": "5.0.4",
+    "@vitest/ui": "5.0.5",
     "jsdom": "27.2.0",
     "happy-dom": "20.0.10",
     "temporal-polyfill": "1.0.4"

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_preview/snapshots/upstream_real_timers.md

@@ -7,5 +7,5 @@ Known upstream regression introduced in Vitest 4.1.1 and still present in 5.0.1,
 ```
 Browser runner started at http://localhost:<port>/__vitest_test__/?sessionId=<uuid>
 
-Known upstream regression since Vitest 4.1.1: Preview locator clicks fail with real timers in 5.0.4
+Known upstream regression since Vitest 4.1.1: Preview locator clicks fail with real timers in 5.0.5
 ```

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_webdriverio/pnpm-workspace.yaml

@@ -1,5 +1,5 @@
 # The community provider accepts newer @vitest/browser patches. Keep this
 # fixture on the bundled runner's version when testing the packed package.
 overrides:
-  '@vitest/browser': 5.0.4
-  vitest: 5.0.4
+  '@vitest/browser': 5.0.5
+  vitest: 5.0.5

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/test_v5_webdriverio/verify.mjs

@@ -78,5 +78,5 @@ try {
   assert.equal(runner.state.getCountOfFailedTests(), 0, JSON.stringify(runner.state.getFiles().flatMap((file) => [file.result, ...file.tasks.map((task) => task.result)])));
   assert.equal(runner.state.getFiles().length, 1);
   assert.ok(sessionOpened);
-  console.log('WebDriverIO 5.0.0 with Vitest 5.0.4: runner/context identity, real-timer clicks, session URLs, and serialized custom-command locators passed');
+  console.log(`WebDriverIO 5.0.0 with Vitest ${runner.version}: runner/context identity, real-timer clicks, session URLs, and serialized custom-command locators passed`);
 } finally { await runner.close(); }

docs/guide/migrate.md

@@ -151,7 +151,7 @@ View and copy this prompt into your coding agent to upgrade an existing Vite+ 0.
 
 ### Vitest
 
-Vitest is automatically migrated through `vp migrate`. `vite-plus` re-exports upstream `vitest@5.0.4` under `vite-plus/test*`, so for node-mode tests a single `vite-plus` install is enough — you no longer need to install `vitest` directly.
+Vitest is automatically migrated through `vp migrate`. `vite-plus` re-exports upstream `vitest@5.0.5` under `vite-plus/test*`, so for node-mode tests a single `vite-plus` install is enough — you no longer need to install `vitest` directly.
 
 For browser mode, you can use the base browser runtime (`@vitest/browser`) and Preview provider (`@vitest/browser-preview`) included in `vite-plus`. To use Playwright or WebDriverIO, you also need the opt-in provider (`@vitest/browser-playwright` or `@vitest/browser-webdriverio`) and its framework peer (`playwright` or `webdriverio`).
 

docs/guide/test.md

@@ -2,7 +2,7 @@
 
 `vp test` runs tests with [Vitest](https://vitest.dev).
 
-Vite+ depends on Vitest `5.0.4`, which requires Node `^22.18.0 || ^24.11.0 || >=26.0.0`. For existing projects, follow [Upgrade to Vitest 5](./vitest-v5.md) before updating dependencies.
+Vite+ depends on Vitest `5.0.5`, which requires Node `^22.18.0 || ^24.11.0 || >=26.0.0`. For existing projects, follow [Upgrade to Vitest 5](./vitest-v5.md) before updating dependencies.
 
 `vp test` resolves Vitest from `vite-plus`'s dependencies first, then from your project.
 

docs/guide/vitest-v5.md

@@ -1,6 +1,6 @@
 # Upgrade to Vitest 5
 
-Vite+ bundles Vitest `5.0.4`. Use Node `^22.18.0 || ^24.11.0 || >=26.0.0` for the CLI and tests.
+Vite+ bundles Vitest `5.0.5`. Use Node `^22.18.0 || ^24.11.0 || >=26.0.0` for the CLI and tests.
 
 ## Before you migrate
 
@@ -126,7 +126,7 @@ Review calls with benchmark options, imported or reassigned callbacks, callback
 
 ## Entry points and packages
 
-Use `vite-plus/test` for assertions and supported runner APIs. Keep coverage providers and `@vitest/ui` at the bundled runner's exact version, `5.0.4`. Keep `@vitest/web-worker` aligned when your project uses it.
+Use `vite-plus/test` for assertions and supported runner APIs. Keep coverage providers and `@vitest/ui` at the bundled runner's exact version, `5.0.5`. Keep `@vitest/web-worker` aligned when your project uses it.
 
 | v4 import                                | v5 import or action                                                         |
 | ---------------------------------------- | --------------------------------------------------------------------------- |

packages/cli/src/utils/constants.ts

@@ -15,7 +15,7 @@ export const VITE_CONFIG_FILES = [
   'vite.config.cts',
 ] as const;
 
-export const VITEST_VERSION = '5.0.4';
+export const VITEST_VERSION = '5.0.5';
 
 // Exact action release used by generated workflows and the @v1 migration.
 // The Renovate custom manager keeps this value current.