build(deps-dev): bump vitest from 4.1.11 to 5.0.0 in the all-dependencies group - #45
Merged
stephendolan merged 2 commits intoSep 29, 2026
Conversation
Bumps the all-dependencies group with 1 update: [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest). Updates `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 dependency-group: all-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Dependabot bumps package.json but not bun.lock in this repo, so `bun install --frozen-lockfile` fails on the PR head and a plain `bun install` silently rewrites the lockfile. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dependabot
Bot
deleted the
dependabot/npm_and_yarn/all-dependencies-4b52c90628
branch
September 29, 2026 14:56
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.
Verification (vitest 4.1.11 → 5.0.x)
Added commit 46ada79: regenerated
bun.lock. Dependabot bumpedpackage.jsononly, sobun install --frozen-lockfilefailed on the PR head ("lockfile had changes, but lockfile is frozen"), and a plainbun installwould have rewritten the lockfile silently. The lockfile now resolvesvitest@5.0.2; the old lock was on 4.0.16.Why the original green check didn't prove anything: CI runs
bun install(not frozen) andbun test(bun's native runner, which remapsvitestimports tobun:test). CI never executes vitest, so a vitest major can't break CI either way.Local results on 46ada79 (clean
node_modules, node 24.14.1, bun 1.3.14):bun install --frozen-lockfilebun run typecheckbun run lintbun run buildbun run test(vitest v5.0.2)bun testThe baseline on
main(vitest 4.0.16) was also 24/24 under both runners, and the same 24 tests ran under v5.Breaking-change review: the tests only use
describe/it/expect/beforeAll, with no vitest config file, mocks,test.each,sequential,expect.poll, snapshots, reporters, or browser mode. vitest 5 requires Node ≥ 22, which already matchesengines.node >=22.12.0. None of the listed breaking changes affect this repo.Bumps the all-dependencies group with 1 update: vitest.
Updates
vitestfrom 4.1.11 to 5.0.0Release 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)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions