chore(deps): update vitest monorepo to ^5.0.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@vitest/coverage-v8 (source)	^5.0.0 → ^5.0.1
vitest (source)	^5.0.0 → ^5.0.1

---

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v5.0.1

Compare Source

   🚀 Features

• ui:
  • Move trace attempts selector to viewer header  -  by @​hi-ogawa, Hiroshi Ogawa and Codex in #​11189 (5dc4b)
  • Add focused trace view layout mode  -  by @​hi-ogawa, Hiroshi Ogawa, OpenCode (gpt-5.6-sol) and Codex in #​11190 (376dc)

   🐞 Bug Fixes

• Exit 1 when vitest list fails collection  -  by @​hamed-bavar in #​11145 and #​11146 (6108b)
• Keep parse error details in static collection  -  by @​hamed-bavar in #​11150 and #​11151 (7c818)
• Avoid recursive prototype in automocking  -  by @​sheremet-va in #​11195 (99fc5)
• Prevent false Vitest import resolution  -  by @​sheremet-va in #​11196 (b426c)
• Keep metadata file when clearing the cache  -  by @​sheremet-va in #​11199 (73614)
• Correct typos in error message and comments  -  by @​shinji00222 and Shinji in #​11187 (115c3)
• Resolve ResolvedConfig exactOptionalPropertyTypes errors  -  by @​LukeAbby in #​11175 (498fb)
• Share the server on self-referencing extends  -  by @​sheremet-va in #​11034 (23dda)
• Warn when deprecated deps.optimizer.web is used  -  by @​im10furry in #​11214 (2ce29)
• browser:
  • Avoid double quotes in config.define  -  by @​sheremet-va in #​11198 (972e2)
• doctor:
  • Measure vm pools for custom environments  -  by @​sheremet-va in #​11212 (91ab1)
• expect:
  • Correct return value in toMatchAriaSnapshot  -  by @​sheremet-va in #​11208 (c119b)
• fakeTimers:
  • Force queueMicrotask and nextTick in toNotFake  -  by @​kingmakeruix, kingmakeruix, Hiroshi Ogawa, Codex and @​hi-ogawa in #​11261 (a47d7)
• snapshot:
  • Report obsolete keys next to skipped tests  -  by @​hamed-bavar, Hiroshi Ogawa and OpenCode (gpt-5.6-sol) in #​11157 and #​11158 (17e2b)
• types:
  • Make public declarations self-contained  -  by @​ZoeySigel in #​11141 (45546)
• ui:
  • Fix collapse/expand suite with file name search  -  by @​hi-ogawa, Hiroshi Ogawa and Codex in #​11260 (0a712)
  • Fix explorer file summary count  -  by @​hi-ogawa, Hiroshi Ogawa, OpenCode (gpt-5.6-sol) and Codex in #​11125 (05982)
• utils:
  • Fix deepMerge to handle prototype  -  by @​hi-ogawa, Hiroshi Ogawa and Codex in #​11215 (4944c)

    View changes on GitHub

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • "every weekend"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Error: ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION

  × installing dependencies
  ╰─▶ 1 lockfile entries failed verification:
        @types/node@22.20.4 was published at 2026-09-19T00:12:01.551Z, within
      the minimumReleaseAge cutoff (2026-09-18T18:26:19.151Z)
  help: The lockfile contains entries that the active policies reject. This
        can mean the lockfile is stale, or that someone committed a lockfile
        that bypassed the policy locally — inspect recent changes to pnpm-
        lock.yaml before trusting it. If the changes look expected, run "pnpm
        clean --lockfile" and then "pnpm install" to rebuild from a fresh
        resolution. Alternatively, relax the policy that flagged them.