diff --git a/pnpm-workspace.yaml b/pnpm-workspace.yaml
index 2f0bd9b..c604bf0 100644
--- a/pnpm-workspace.yaml
+++ b/pnpm-workspace.yaml
@@ -8,14 +8,14 @@ allowBuilds:
   workerd: true
   sharp: true
   better-sqlite3: false
-# vite-plus and the @voidzero-dev/vite-plus-* packages are excluded from
-# pnpm's release-age cooldown:
-# Renovate's vite+ fast lane (github>Boshen/renovate) proposes their bumps
-# immediately, and this repo dogfoods fresh Vite+ releases.
+# vite-plus, the @voidzero-dev/vite-plus-* packages, and vitest are excluded
+# from pnpm's release-age cooldown. The local Renovate vite+ group proposes
+# their bumps together and immediately, and this repo dogfoods fresh releases.
 minimumReleaseAgeExclude:
   - void@0.10.5
   - vite-plus
   - '@voidzero-dev/vite-plus-*'
+  - vitest
 catalog:
   vite: npm:@voidzero-dev/vite-plus-core@0.2.9
   vitest: 4.1.10
diff --git a/renovate.json b/renovate.json
index 6fc0bcf..d3c5709 100644
--- a/renovate.json
+++ b/renovate.json
@@ -2,10 +2,17 @@
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
   "extends": ["config:recommended", "github>Boshen/renovate"],
   "description": [
-    "The shared preset sets a 3-day minimumReleaseAge for npm and GitHub Actions updates, clearing pnpm 11's 1-day supply-chain cooldown on `pnpm install --frozen-lockfile` (a too-new lockfile entry fails CI with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION). internalChecksFilter=strict holds such an update until it ages in, instead of opening a red PR. The preset's vite+ group updates vite-plus and @voidzero-dev/vite-plus-* immediately; pnpm-workspace.yaml excludes those packages from the cooldown so their bumps install."
+    "The shared preset sets a 3-day minimumReleaseAge for npm and GitHub Actions updates, clearing pnpm 11's 1-day supply-chain cooldown on `pnpm install --frozen-lockfile` (a too-new lockfile entry fails CI with ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION). internalChecksFilter=strict holds such an update until it ages in, instead of opening a red PR. The local vite+ group updates vite-plus, @voidzero-dev/vite-plus-*, and vitest immediately; pnpm-workspace.yaml excludes those packages from the cooldown so their bumps install."
   ],
   "internalChecksFilter": "strict",
   "packageRules": [
+    {
+      "description": "Group Vite+, its package aliases, and Vitest into a single PR so a Vite+ upgrade cannot omit its required Vitest version. minimumReleaseAge and schedule keep every package on the same immediate-update policy; the preset's generic npm rule would otherwise hold the aliases and Vitest behind a 3-day age gate and a Monday schedule.",
+      "groupName": "vite+",
+      "matchPackageNames": ["vite-plus", "@voidzero-dev/vite-plus-*", "vitest"],
+      "minimumReleaseAge": "0 days",
+      "schedule": ["at any time"]
+    },
     {
       "description": [
         "nanotar (bundled) and vite-plus (whose `vp pack` is the bundler) both shape the committed publish-action bundle (.github/actions/publish-preview/dist). A bump to either can change that bundle, so flag those PRs with `needs-bundle-rebuild`, which triggers the rebuild-bundle workflow to re-run `vp run build:action` and push the refreshed dist; the 'Verify action bundle' CI check is the backstop for anything else."