Skip to content

chore: bump @vitest/coverage-v8 from 4.1.11 to 5.0.0 - #123

Merged
danielsimonjr merged 2 commits into
masterfrom
dependabot/npm_and_yarn/vitest/coverage-v8-5.0.0
Sep 7, 2026
Merged

chore: bump @vitest/coverage-v8 from 4.1.11 to 5.0.0#123
danielsimonjr merged 2 commits into
masterfrom
dependabot/npm_and_yarn/vitest/coverage-v8-5.0.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 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 @github

dependabot Bot commented on behalf of github Sep 7, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: npm. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 7, 2026
@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

Major version update — not auto-merged.

@vitest/coverage-v8
4.1.115.0.0

Check before merging:

  • Does the new version's engines still satisfy this package's own
    engines floor? A runtime dependency that raises its Node floor
    above ours is a breaking change for consumers, and no typecheck
    or test on a newer runner will catch it.
  • Is this a runtime dependency or a devDependency? A dev-only
    bump cannot break an installed consumer.

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 force-pushed the dependabot/npm_and_yarn/vitest/coverage-v8-5.0.0 branch from 9600444 to 46b58d7 Compare September 7, 2026 20:05
@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown

Major version update — not auto-merged.

@vitest/coverage-v8
4.1.115.0.0

Check before merging:

  • Does the new version's engines still satisfy this package's own
    engines floor? A runtime dependency that raises its Node floor
    above ours is a breaking change for consumers, and no typecheck
    or test on a newer runner will catch it.
  • Is this a runtime dependency or a devDependency? A dev-only
    bump cannot break an installed consumer.

Dependabot edits package.json without touching bun.lock (it uses the npm
ecosystem, because its bun parser caps at lockfileVersion 1 while Bun 1.4
writes 2), so CI fails at `bun install --frozen-lockfile` before any test runs.

This pair had to land in order: coverage-v8 5 against a vitest 4 core fails
with "coverageFilesDirectory is required". #122 moved the core first, and
Dependabot then rebased this branch onto it on its own.

Regenerated under Bun 1.4.2 on top of that rebase. Frozen install clean (199
installs), suite green: 321 files, 7843 tests.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EiXPsQY8g2uq159wY2uemT
@danielsimonjr
danielsimonjr merged commit 95a419d into master Sep 7, 2026
7 checks passed
@danielsimonjr
danielsimonjr deleted the dependabot/npm_and_yarn/vitest/coverage-v8-5.0.0 branch September 7, 2026 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant