chore(deps-dev): bump vitest and @vitest/coverage-v8 to 4.1.11 together - #109
Merged
Merged
Conversation
Dependabot split this one upgrade across two PRs (#94 bumps `vitest`, #95 bumps `@vitest/coverage-v8`), and neither can pass on its own: each leaves the pair straddling 4.1.10 and 4.1.11, and npm refuses to install it. npm error code ERESOLVE npm error While resolving: @vitest/coverage-v8@4.1.10 Both have therefore been red on `test`, `coverage` and `quality` since 2026-08-24. `package.json` also overrides html-validate's nested vitest with `$vitest`, so the direct dependency's version has to be the one that moves. Moving both in one commit. Verified locally: npm ci clean, then check, lint, test:i18n, validate:digests, test (92 passed), build, validate:html and test:coverage (97.59% statements) all green. Closes #94 Closes #95
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
verbara-website | 2ecf63f | Commit Preview URL Branch Preview URL |
Sep 20 2026, 01:23 PM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why this exists instead of #94 / #95
Dependabot split one upgrade into two PRs, and neither can ever go green alone:
vitest4.1.10 → 4.1.11, leaving@vitest/coverage-v8at 4.1.10.@vitest/coverage-v84.1.10 → 4.1.11, leavingvitestat 4.1.10.Either way the pair straddles two versions and npm refuses to install:
That is why both have been red on
test,coverageandqualitysince 2026-08-24 — the failure is at install time, before a single test runs.package.jsonadditionally overrides html-validate's nested vitest with"vitest": "$vitest", so the direct dependency's version is the one that has to move.This PR moves both in one commit.
Verified locally
npm ciresolves clean, then the full CI lane:npm run checknpm run lintnpm run test:i18nnpm run validate:digestsnpm testnpm run buildnpm run validate:htmlnpm run test:coverageLockfile confirms both
node_modules/vitestandnode_modules/@vitest/coverage-v8at4.1.11.Follow-up worth doing
Add a dependabot group for
vitest/@vitest/*so this pair never gets split again — otherwise the next patch release reproduces exactly this stalemate.Closes #94
Closes #95