deps: bump vitest from 4.1.11 to 5.0.0 - #17
Merged
Merged
Conversation
cldmv-bot
Bot
added
the
type: dependencies
Contributor
|
@dependabot recreate |
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
Bot
force-pushed
the
dependabot/npm_and_yarn/next/vitest-5.0.0
branch
from
September 13, 2026 22:00
26b250b to
e18492a
Compare
@vitest/coverage-v8 peers vitest with a major-locked range, so Dependabot's separate vitest-only bump (this branch) broke npm ci with an ERESOLVE until coverage-v8 moved too. `@dependabot recreate` does not re-group an already-opened single-package PR against a newly added dependabot.yml group -- it just refreshes that PR's own single-package update, so this had to be applied by hand. Also fixes a real regression vitest 5 surfaced: it defaults clearMocks to true (was false in vitest 4), so tests/port-fallback.test.vitest.mjs's second assertion checked a mock call history vitest had already auto-cleared before that test ran. Snapshot the observed log call once, right after it happens in beforeAll, instead of asserting against the spy's live state later.
cldmv-bot
Bot
added
the
area: tests
Shinrai
approved these changes
Sep 13, 2026
dependabot
Bot
deleted the
dependabot/npm_and_yarn/next/vitest-5.0.0
branch
September 13, 2026 22:16
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.
Bumps vitest from 4.1.11 to 5.0.0.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
f441c6fchore: release v5.0.0 (#11130)d46a747fix: treat test.describe as a suite during static collection (#11128)584cf30fix: add a warning if inline project has duplicate plugins due to unexpected ...f08ce4bfix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)897f51fchore: release v5.0.0-rc.4 (#11107)1339b06chore(deps): update all non-major dependencies (#11104)51e9494feat!: parse files statically in vitest list by default (#11088)2122ffdfix: propagate --maxWorkers to projects (#11102)dc10f5ffix(browser): report the action error when a task times out (#11101)d4fe198feat: promote clearCache out of experimental (#11086)