Keep Vitest major upgrades coordinated

The isolated coverage-v8 5 proposal cannot install beside Vitest 4 because its peer range requires Vitest 5. Ignore only version majors for both packages until a reviewed frontend migration can update and prove the pair together; retain grouped security updates and minor/patch updates.

Change-source: pulse-maintainer

.github/dependabot.yml

@@ -130,6 +130,15 @@ updates:
       - dependency-name: "lucide-solid"
         update-types:
           - "version-update:semver-major"
+      # Vitest and its V8 coverage provider require matching major versions.
+      # An isolated coverage-v8 5.x update cannot install beside Vitest 4.x;
+      # migrate the pair with frontend proof as one explicit change instead.
+      - dependency-name: "vitest"
+        update-types:
+          - "version-update:semver-major"
+      - dependency-name: "@vitest/coverage-v8"
+        update-types:
+          - "version-update:semver-major"
 
   - package-ecosystem: "docker"
     directories:

scripts/tests/test_dependabot_config.py

@@ -157,13 +157,21 @@ class DependabotConfigTest(unittest.TestCase):
                 "typescript",
                 "eslint",
                 "lucide-solid",
+                "vitest",
+                "@vitest/coverage-v8",
             },
         )
         for browser_runtime in ("playwright", "playwright-core", "@playwright/test"):
             self.assertEqual(ignored[browser_runtime], all_semver)
         # These majors require an explicit toolchain or icon-import migration.
         # Minor and patch version updates must remain eligible for Dependabot.
-        for dependency in ("typescript", "eslint", "lucide-solid"):
+        for dependency in (
+            "typescript",
+            "eslint",
+            "lucide-solid",
+            "vitest",
+            "@vitest/coverage-v8",
+        ):
             self.assertEqual(
                 ignored[dependency],
                 {"version-update:semver-major"},