[dependabot]

Bumps @vitest/mocker to 4.1.12 and updates ancestor dependency vitest. These dependencies need to be updated together.

Updates @vitest/mocker from 4.1.11 to 4.1.12

Release notes

Sourced from @​vitest/mocker's releases.

v4.1.12

   🐞 Bug Fixes

• mocker: Harden manual and redirect mocks [backport to v4]  -  by @​sheremet-va in vitest-dev/vitest#11580 (b8253)

    View changes on GitHub

Commits

• 4766ce1 chore: release v4.1.12 (#11610)
• b825313 fix(mocker): harden manual and redirect mocks [backport to v4] (#11580)
• See full diff in compare view

Updates vitest from 4.1.11 to 4.1.12

Release notes

Sourced from vitest's releases.

v4.1.12

   🐞 Bug Fixes

• mocker: Harden manual and redirect mocks [backport to v4]  -  by @​sheremet-va in vitest-dev/vitest#11580 (b8253)

    View changes on GitHub

Commits

• 4766ce1 chore: release v4.1.12 (#11610)
• 5bf2197 chore: delete wdio folder from v4 branch to avoid falsy release (#11581)
• 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 — dependency bump audit

Semver risk: patch (4.1.11 → 4.1.12 for both vitest and @vitest/mocker). Low risk — same major/minor line, no API surface changes expected.

Changes in this release: Single fix in v4.1.12 — "mocker: Harden manual and redirect mocks" (backported to v4), vitest-dev/vitest#11580. This is a security fix, not a routine patch:

• CVE-2026-112950 / GHSA-xp26-3454-mjgp (medium, CVSS 5.9) — the fix for the earlier path-traversal advisory (GHSA-82fw-gwwq-j7x9, CVE-2026-84373) joined the redirect URL pathname with node:path/posix, which doesn't normalize \ on Windows. A redirect mock using ..\secret.txt bypassed the allowlist check and let readFile() read files outside the configured dev-server root. 4.1.12 converts backslashes to forward slashes before the allowlist check, closing the bypass.
• This repo currently has an open Dependabot alert for exactly this advisory (alert Yellow-hat: Labro's architectural discipline as its core differentiator — leverage docs, perspectives system, and multi-provider architecture more aggressively #37, @vitest/mocker >= 4.1.11, < 4.1.12) — this PR is the fix.

Lock file: Mostly a clean lockstep bump of the @vitest/* family (expect/mocker/pretty-format/runner/snapshot/spy/utils) to 4.1.12, as expected for a monorepo release. Two incidental transitive upgrades within existing caret ranges, both harmless dev-only deps:

• chai 6.2.2 → 6.3.0 (peer dep of @vitest/expect, range ^6.2.2)
• tinyrainbow 3.1.1 → 3.2.0 (peer dep of @vitest/mocker/utils, range ^3.1.0)

Prior pins: None found. git log shows a clean progression of routine Dependabot vitest bumps (4.1.10→4.1.11 in #68, now 4.1.11→4.1.12 here) with no manual pin or comment referencing vitest/@vitest/mocker in between.

Conflict check: Clean. mergeable: MERGEABLE, and the build check (which runs npm ci against this exact lock file) is green.

CI: ✅ passing — ci-dashboard.yml / build check succeeded (npm ci + vitest + tsc -b && vite build).

Recommendation: ✅ Safe to merge — low-risk patch bump that also closes an open, actively-tracked security advisory (CVE-2026-112950) on a dev-time dependency. Not merging myself per harness policy; flagging as a good candidate for prompt merge given the open advisory.