chore(deps-dev): bump vitest from 4.1.10 to 4.1.11 in /dashboard

[dependabot]

Bumps vitest from 4.1.10 to 4.1.11.

Release notes

Sourced from vitest's releases.

v4.1.11

   🐞 Bug Fixes

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

    View changes on GitHub

Commits

• 9bd8d46 chore: release v4.1.11 (#10995)
• 9851dbc fix(browser): trigger playwright/chromium gc on lower disk availability [back...
• See full diff 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[labro-bot]

Labro picking up. Assigning to claude-code:claude-sonnet-5.

[labro-bot]

Maintainer review — vitest 4.1.10 → 4.1.11 (dashboard, dev dependency)

Semver risk: patch — same major/minor, patch-only bump. Low risk.

Changes in this release (v4.1.11):

• Revived the global concurrency limit for test lifecycle (backported to v4)
• browser: encode iframeId in tester iframe URL; trigger Playwright/Chromium GC on low disk availability
• mocker: restrict redirect mocks to the fs allowlist — this is the fix for a security advisory (see below)

No breaking changes or deprecations noted.

Security: this bump fixes GHSA-82fw-gwwq-j7x9 / CVE-2026-84373 — "Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock" (severity: MODERATE), affecting vitest >= 2.1.0, < 4.1.11. 4.1.10 (the version this PR replaces) is in the vulnerable range. Since vitest is a devDependency used only for running tests, exposure is limited to local/CI test execution rather than production, but this is still a legitimate reason to take the bump promptly. Not flagged as a security PR by Dependabot's labels here (dependencies, javascript only), but the CVE applies.

Lock file: clean. dashboard/package-lock.json only touches vitest and its own @vitest/* scoped packages (coverage-v8, expect, mocker, pretty-format, runner, snapshot, spy, utils), all moving uniformly 4.1.10 → 4.1.11. No unrelated transitive packages changed. package.json's vitest range also widened from ^4.1.9 to ^4.1.11 (standard Dependabot behavior for a direct dependency bump).

Prior pins: none found. No manual pin of vitest and no commit/comment in git history constraining it below 4.1.11 — recent dashboard-deps history (32e6005, e1b8e9d, cbe616c, 0c10409) shows only routine automated bumps.

Conflict check: not independently re-run locally — this sandboxed session blocks git fetch/git checkout of the PR branch (requires interactive approval that isn't available in this unattended run). However, the build check on this exact head commit (which runs npm ci + vitest + tsc -b && vite build per ci-dashboard.yml) completed successfully, which is functionally equivalent to a clean resolver run.

CI: passing — build check is green on the head commit.

Recommendation: ✅ Safe to merge — patch-level bump, clean lock file diff scoped to the vitest package family, no conflicting prior pins, CI green, and it happens to close out a moderate-severity path traversal advisory in the mocker package as a bonus.