Skip to content

chore: bump vitest from 4.1.11 to 5.0.0 - #122

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

chore: bump vitest from 4.1.11 to 5.0.0#122
danielsimonjr merged 2 commits into
masterfrom
dependabot/npm_and_yarn/vitest-5.0.0

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Bumps vitest from 4.1.11 to 5.0.0.

Release notes

Sourced from vitest'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
  • f441c6f chore: release v5.0.0 (#11130)
  • d46a747 fix: treat test.describe as a suite during static collection (#11128)
  • 584cf30 fix: add a warning if inline project has duplicate plugins due to unexpected ...
  • f08ce4b fix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)
  • 897f51f chore: release v5.0.0-rc.4 (#11107)
  • 1339b06 chore(deps): update all non-major dependencies (#11104)
  • 51e9494 feat!: parse files statically in vitest list by default (#11088)
  • 2122ffd fix: propagate --maxWorkers to projects (#11102)
  • dc10f5f fix(browser): report the action error when a task times out (#11101)
  • d4fe198 feat: promote clearCache out of experimental (#11086)
  • Additional commits viewable in compare view

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)

Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) 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/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@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
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 uses the npm ecosystem (its bun parser caps at lockfileVersion 1 and
Bun 1.4 writes 2), so it edits package.json without touching bun.lock. CI then
fails at `bun install --frozen-lockfile` before a single test runs.

Regenerated under Bun 1.4.2. Frozen install clean (209 installs, no changes),
suite green: 321 test files pass.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01EiXPsQY8g2uq159wY2uemT
@danielsimonjr
danielsimonjr merged commit 62b3e53 into master Sep 7, 2026
7 checks passed
@danielsimonjr
danielsimonjr deleted the dependabot/npm_and_yarn/vitest-5.0.0 branch September 7, 2026 20:03
danielsimonjr added a commit that referenced this pull request Sep 7, 2026
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 added a commit that referenced this pull request Sep 7, 2026
* chore: bump @vitest/coverage-v8 from 4.1.11 to 5.0.0

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>

* build(deps): regenerate bun.lock for @vitest/coverage-v8 5.0.0

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

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: DANIEL SIMON JR <1813231+danielsimonjr@users.noreply.github.com>
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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant