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
This commit is contained in:
pulse-triage[bot]
2026-09-27 10:10:45 +01:00
parent 6a9db329a7
commit c0cfa8ef7e
2 changed files with 18 additions and 1 deletions
+9
View File
@@ -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: