Skip to content

chore(deps-dev): bump vitest from 4.1.11 to 5.0.0 - #265

Merged
Bccorb merged 2 commits into
mainfrom
dependabot/npm_and_yarn/vitest-5.0.0
Sep 8, 2026
Merged

chore(deps-dev): bump vitest from 4.1.11 to 5.0.0#265
Bccorb merged 2 commits into
mainfrom
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 dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 7, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/vitest-5.0.0 branch from 7e7ca29 to a93cf84 Compare September 7, 2026 22:01
dependabot Bot and others added 2 commits September 8, 2026 15:47
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>
The vitest bump alone did not install. @vitest/coverage-v8 declares an exact peer
on vitest, so holding it at 4.1.11 while vitest went to 5.0.0 made npm ci fail
with ERESOLVE, which is what broke both the test job and the docker build inside
verify rather than any test failure.

Move the two together and regenerate the lockfile on top of current main. The
lockfile churn is confined to the vitest packages and the istanbul reporters that
coverage-v8 pulls in.
@Bccorb
Bccorb force-pushed the dependabot/npm_and_yarn/vitest-5.0.0 branch from a93cf84 to 1c17d6e Compare September 8, 2026 19:51
@Bccorb

Bccorb commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

The bump alone could not install. @vitest/coverage-v8 declares an exact peer on vitest, so
holding it at 4.1.11 while vitest moved to 5.0.0 made npm ci fail with ERESOLVE. That is what
broke both the test job and the Docker build inside verify, rather than any test failure.

Pushed two changes on top:

  • @vitest/coverage-v8 moves to ^5.0.0 with vitest, so the peer is satisfied.
  • Rebased onto current main and regenerated the lockfile there. Main has touched
    package-lock.json in three commits since this branch was cut, so regenerating on the old base
    would likely have conflicted.

Lockfile churn is confined to the vitest packages and the istanbul reporters coverage-v8 pulls in.
No unrelated dependency moved.

Verified locally on the rebased branch: npm ci resolves, typecheck, lint and format:check are
clean, npm run build succeeds, tests are 114 files and 1374 passed (1 skipped, 1 todo) on vitest
5.0.0, and npm run coverage reports 98.82% statements and 96.09% branches, above the configured
thresholds. Node 24 satisfies vitest 5's engines range.

Since the branch now carries a non-dependabot commit, dependabot will stop updating it.

@Bccorb
Bccorb merged commit b5c3081 into main Sep 8, 2026
5 checks passed
@Bccorb
Bccorb deleted the dependabot/npm_and_yarn/vitest-5.0.0 branch September 8, 2026 19:54
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 javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant