chore(deps): update vitest monorepo to v4.1.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@vitest/coverage-v8 (source)	4.1.10 → 4.1.11
@vitest/ui (source)	4.1.10 → 4.1.11

---

Release Notes

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

v4.1.11

Compare Source

   🐞 Bug Fixes

• Revive global concurrency limit for test lifecycle [backport to v4]  -  by @​sheremet-va and @​hi-ogawa in #​10992 (5146d)
• browser:
  • Encode iframeId in tester iframe URL [backport to v4]  -  by @​sheremet-va, Pduhard and Claude Opus 4.8 in #​10955 (10b2c)
  • Trigger playwright/chromium gc on lower disk availability [backport to v4]  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode in #​10951 (9851d)
• mocker:
  • Restrict redirect mocks to the fs allowlist [backport to v4]  -  by @​sheremet-va in #​10974 (fe5a1)

    View changes on GitHub

---

Configuration

📅 Schedule: (in timezone Etc/UTC)

• Branch creation
  • Between 12:00 AM and 12:59 AM, on day 1 of the month (* 0 1 * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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: package-lock.json

npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @acarshub/backend@4.2.2
npm error Found: vitest@4.1.10
npm error node_modules/vitest
npm error   dev vitest@"4.1.10" from @acarshub/backend@4.2.2
npm error   acarshub-backend
npm error     @acarshub/backend@4.2.2
npm error     node_modules/@acarshub/backend
npm error       workspace acarshub-backend from the root project
npm error   peer vitest@"4.1.10" from @vitest/browser-playwright@4.1.10
npm error   node_modules/@vitest/browser-playwright
npm error     peerOptional @vitest/browser-playwright@"4.1.10" from vitest@4.1.10
npm error   4 more (@vitest/browser-preview, ...)
npm error
npm error Could not resolve dependency:
npm error peer vitest@"4.1.11" from @vitest/coverage-v8@4.1.11
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"4.1.11" from @acarshub/backend@4.2.2
npm error   acarshub-backend
npm error     @acarshub/backend@4.2.2
npm error     node_modules/@acarshub/backend
npm error       workspace acarshub-backend from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-11T03_48_15_645Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-11T03_48_15_645Z-debug-0.log