chore: bump vitest from 4.1.11 to 5.0.0

[dependabot]

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

• Replace loupe.inspect with pretty-format  -  by @​hi-ogawa, Claude Opus 5 (1M context) and OpenAI Codex in vitest-dev/vitest#9609 (3f802)
• Remove quotes from string values in test.for/each title $ variable (take 2)  -  by @​hi-ogawa in vitest-dev/vitest#10170 (04d37)
• Default attachmentsDir from .vitest-attachements/ to .vitest/attachments/  -  by @​MdSadiqMd in vitest-dev/vitest#10186 (1ba73)
• Remove sequential test/suite options in favor of concurrent  -  by @​hi-ogawa and OpenAI Codex in vitest-dev/vitest#10198 (9229f)
• Represent locator as an object instead of a string  -  by @​sheremet-va in vitest-dev/vitest#10212 (80f07)
• Inline expect package  -  by @​sheremet-va in vitest-dev/vitest#10221 (ad162)
• Remove deprecated entry points  -  by @​sheremet-va in vitest-dev/vitest#10222 (994c6)
• Require Node.js 22 and Vite 6.4  -  by @​sheremet-va in vitest-dev/vitest#10178 (38762)
• Fail expect.poll when function didn't resolve in time  -  by @​hi-ogawa and OpenAI Codex in vitest-dev/vitest#10233 (4df04)
• Throw an error if hoistable methods are outside the top level scope  -  by @​sheremet-va in vitest-dev/vitest#10460 (d0b4f)
• toHaveTextContent is strict, add toMatchTextContent as alternative  -  by @​sheremet-va in vitest-dev/vitest#10473 (18f30)
• Don't lookup config file from ancestor directories  -  by @​hi-ogawa, OpenAI Codex and Hiroshi Ogawa in vitest-dev/vitest#10428 (945d9)
• Inline @vitest/runner package, do not publish it anymore  -  by @​sheremet-va in vitest-dev/vitest#10511 (6d6e4)
• Allow mutating happy-dom/jsdom window object  -  by @​hi-ogawa, Hiroshi Ogawa and OpenAI Codex in vitest-dev/vitest#10373 (206e8)
• Expose concurrencyId/workerId on TestModule's diagnostics, make id 1-based  -  by @​sheremet-va in vitest-dev/vitest#10516 (bdd98)
• Add screenshotDirectory config to browser.expect.toMatchScreenshot  -  by @​macarie in vitest-dev/vitest#10592 (a60de)
• Update @sinonjs/fake-timers and support mocking Temporal  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode (gpt-5.6-sol) in vitest-dev/vitest#10654 (f8b15)
• Remove webdriverio package  -  by @​sheremet-va in vitest-dev/vitest#10675 (5fed6)
• Clear mocks by default before each test  -  by @​sheremet-va in vitest-dev/vitest#10613 (0f646)
• Don't emit localStorage warnings on Node 26, fail gracefully when worker fails to start  -  by @​sheremet-va in vitest-dev/vitest#10293 (334ed)
• Separate config resolution from the server creation  -  by @​sheremet-va in vitest-dev/vitest#10554 (1c0ec)
• Inline projects extend the root config by default  -  by @​sheremet-va in vitest-dev/vitest#10750 (fec00)
• Enable mocking Temporal without fake timers  -  by @​fabon-f, Hiroshi Ogawa and OpenCode (gpt-5.6-sol) in vitest-dev/vitest#10757 (ac2d4)
• Support nested projects  -  by @​sheremet-va in vitest-dev/vitest#10846 (ec367)
• Use > as separator in -t, calculate only once  -  by @​sheremet-va in vitest-dev/vitest#10686 (a0b20)
• Fail the test when an asynchronous assertion is not awaited  -  by @​sheremet-va in vitest-dev/vitest#10868 (86d4a)
• Share the Vite server between inline projects  -  by @​sheremet-va in vitest-dev/vitest#10848 (d87c9)
• Parse files statically in vitest list by default  -  by @​sheremet-va in vitest-dev/vitest#11088 (51e94)
• benchmark:
  • Rewrite the public API  -  by @​sheremet-va in vitest-dev/vitest#10113 (19f6e)
• browser:
  • Iframe scale  -  by @​macarie in vitest-dev/vitest#9745 (b6398)
  • Enable locators.exact by default  -  by @​sheremet-va in vitest-dev/vitest#10430 (e2032)
  • Require sessionId for orchestrator html request  -  by @​hi-ogawa, Hiroshi Ogawa and OpenAI Codex in vitest-dev/vitest#10522 (79b7d)
  • Save failure screenshots in attachmentsDir  -  by @​macarie in vitest-dev/vitest#10917 (3b5bb)
• coverage:
  • include/exclude globs too eager  -  by @​AriPerkkio in vitest-dev/vitest#9818 (edacb)
  • Allow thresholds.perFile to accept an object  -  by @​vladlenskiy and @​AriPerkkio in vitest-dev/vitest#10190 (13b78)
• expect:
  • Fix toThrow("") behavior by reverting #6710  -  by @​hi-ogawa in vitest-dev/vitest#9643 and vitest-dev/vitest#6710 (6c3e4)
• mocker:
  • Deserialize automock as automock  -  by @​nami8824 in vitest-dev/vitest#10192 (2f892)
• reporters:
  • blob reporter and --merge-reports default to .vitest/blob/  -  by @​AriPerkkio in vitest-dev/vitest#10232 (d22b0)
  • Write json and junit reporter output files to .vitest by default  -  by @​hi-ogawa, Hiroshi Ogawa, OpenCode (gpt-5.6-sol) and @​AriPerkkio in vitest-dev/vitest#10621 (58577)

... (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 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)

[claude]

Claude finished @dependabot[bot]'s task in 1m 38s —— View job

---

Dependency review: vitest 4.1.11 → 5.0.0 (major)

• Gather context (diff, engines, CI matrix, lockfile)
• Check vitest 5 breaking changes against actual repo usage
• Verify CI result
• Post review

Verdict: safe to merge. CI is green on both Node 22 and 24 (run), and none of vitest 5's breaking changes touch code in this repo.

What changed

Dev-only bump. package.json moves vitest ^4.1.10 → ^5.0.0; the lockfile resolves vitest 5.0.0 and drops the now-inlined @vitest/runner / @vitest/expect packages (vitest 5 inlines expect and runner and stops publishing them). vite is unchanged at 8.2.2 — already inside vitest 5's new ^6.4.0 || ^7 || ^8 peer range, so no transitive Vite major came along.

Breaking changes checked against this codebase

vitest 5 breaking change	Impact here
Requires Node 22 / Vite 6.4	Floor is already >=22, Vite is 8.2.2 — see inline note on the exact patch level
Clear mocks by default before each test	No effect. Every mock is constructed per-test — inside it (test/tools/execute-action.test.ts) or inside beforeEach (test/client/kosli-client.test.ts:87) — so nothing is shared across tests. clearMocks also only clears call history, not implementations
Don't look up config from ancestor dirs	No vitest.config.* exists at all; the suite runs on defaults
Remove deprecated entry points	All 8 test files import from bare "vitest" only
Inline expect / @vitest/runner	Neither is imported directly
Fail on un-awaited async assertions	Would surface as failures — suite passes, so none present
toThrow(""), test.for/each $ titles, sequential, expect.poll, locators, benchmark/browser/coverage/reporter changes	None of these APIs are used anywhere in test/

The suite uses only describe/it/expect/vi.fn/beforeEach/afterEach, which is why the blast radius is so small — the catalog-driven design keeps tests to plain assertions plus an injected fetchFn, with no module mocking, fake timers, or snapshots.

One thing to note

vitest 5's own engines is ^22.12.0 || ^24.0.0 || >=26.0.0, slightly narrower than this repo's ">=22". Dev-only and CI-safe; details in the inline comment.

Not done

I couldn't run npm ci / npm test locally in this sandbox (install requires approval), so the verification above rests on the repo's own CI run rather than a local execution.
· branch dependabot/npm_and_yarn/vitest-5.0.0

[claude]

Heads-up (non-blocking): vitest 5 declares engines.node: "^22.12.0 || ^24.0.0 || >=26.0.0", but this repo declares "node": ">=22" (package.json:13). A contributor on Node 22.0–22.11 — or on an odd release like 23/25 — now gets EBADENGINE on npm install, even though the repo says they're supported.

It's dev-only, so the published package and .mcpb bundle are unaffected, and CI is fine (setup-node with '22' resolves to the latest 22.x). Per CLAUDE.md, raising the real floor means moving engines, manifest.json, README.md, both workflows and @types/node together — probably not worth it just for a devDependency. Worth a line in CONTRIBUTING.md instead if it bites anyone.