Skip to content

build(deps-dev): bump @vitest/coverage-v8 from 4.1.11 to 5.0.0 - #182

Closed
dependabot[bot] wants to merge 1 commit into
frontendfrom
dependabot/npm_and_yarn/frontend/vitest/coverage-v8-5.0.0
Closed

build(deps-dev): bump @vitest/coverage-v8 from 4.1.11 to 5.0.0#182
dependabot[bot] wants to merge 1 commit into
frontendfrom
dependabot/npm_and_yarn/frontend/vitest/coverage-v8-5.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 12, 2026

Copy link
Copy Markdown
Contributor

Bumps @vitest/coverage-v8 from 4.1.11 to 5.0.0.

Release notes

Sourced from @​vitest/coverage-v8's releases.

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
build(deps-dev): bump @vitest/coverage-v8 from 4.1.11 to 5.0.0
726eeb0 
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 4.1.11 to 5.0.0.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/coverage-v8)

---
updated-dependencies:
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 12, 2026
This was referenced Sep 13, 2026
Merged
Merged
bgard68 added a commit that referenced this pull request Sep 13, 2026
@bgard68 @claude
build(deps-dev): bump vitest and coverage-v8 to 5.0.0 together (#189)
7ff76fe 
@vitest/coverage-v8 declares an exact peer on vitest, so the two cannot
move independently. Dependabot opened them as separate pull requests
(#183 bumped vitest, #182 bumped coverage-v8) and each one broke npm
install on its own branch:

  npm error Could not resolve dependency:
  npm error peer vitest@"4.1.11" from @vitest/coverage-v8@4.1.11
  npm error Conflicting peer dependency: vitest@4.1.11

Neither could ever go green alone, and no rebase would help — the fix
has to be one commit that moves both. This is the same failure mode the
dependabot.yml comment already documents for codeql-action's sub-actions.

Verified on the upgrade: 20 test files, 287 tests passing, coverage
reporting intact (99.39% statements, 100% lines/functions) and
`vite build` clean.

Supersedes #182 and #183.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
@bgard68

bgard68 commented Sep 13, 2026

Copy link
Copy Markdown
Owner

Superseded by #189, now merged into frontend.

This PR could not go green on its own: @vitest/coverage-v8 declares an exact peer dependency on vitest, so bumping one side alone leaves npm ci unsatisfiable —

npm error Could not resolve dependency:
npm error peer vitest@"4.1.11" from @vitest/coverage-v8@4.1.11
npm error Conflicting peer dependency: vitest@4.1.11

— which is why both Build & Deploy Frontend and Build web image & scan failed here. No rebase could have fixed it; the two versions had to move in a single commit.

#189 bumps both to 5.0.0 together and is green on every check, with 287 tests passing and coverage reporting intact.

The reason Dependabot split them in the first place is that the npm entry groups ["minor", "patch"] only, so a major bypasses the group. #190 adds a vitest group spanning all update types so the next major arrives as one PR.

@bgard68 bgard68 closed this Sep 13, 2026
@dependabot @github

dependabot Bot commented on behalf of github Sep 13, 2026

Copy link
Copy Markdown
Contributor Author

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/frontend/vitest/coverage-v8-5.0.0 branch September 13, 2026 14:15
bgard68 added a commit that referenced this pull request Sep 13, 2026
@bgard68 @claude
build(deps): group the vitest packages across all update types (#190)
3c0b888 
The npm entry grouped ["minor", "patch"] only, so a major bypassed the
group and arrived one pull request per package. @vitest/coverage-v8
pins vitest with an exact peer, so that split produced two branches
that could never go green: #182 and #183, each failing `npm ci` with
ERESOLVE against the other's version.

github-actions is already grouped across all update types in this file
for precisely this reason - codeql-action's sub-actions must match, and
that holds regardless of bump size. The vitest pair has the same
property, so it gets the same treatment.

Listed before the catch-all group, because Dependabot assigns a
dependency to the first group whose patterns match it.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@bgard68