fix(deps): update dependency vitest (4.1.6 → 4.1.7)

[miso-assistant]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vitest (source)	4.1.6 → 4.1.7

---

Release Notes

vitest-dev/vitest (vitest)

v4.1.7

Compare Source

   🐞 Bug Fixes

• runner: Limit concurrency per task branch in addition to per leaf callbacks (backport)  -  by @​hi-ogawa in #​10384 (4f0f2)

    View changes on GitHub

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 this update again.

---

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

---

This PR has been generated by Renovate Bot.

[miso-assistant]

✅ Automated recommendation: APPROVE

Analysis engine: anthropic/MiniMax-M2.7@https://litellm.jory.dev/v1 (anthropic)

PR Review: vitest 4.1.6 → 4.1.7

Recommendation: Approve

This is a routine dev-dependency patch update for the vitest monorepo, generated by Renovate bot. The change is low-risk and appears correct.

---

Change-by-Change Findings

1. package-lock.json — vitest monorepo dependency update

• Change: Updated vitest and all @vitest/* subpackages from 4.1.6 → 4.1.7
• Packages affected:
  • vitest (main package)
  • @vitest/expect, @vitest/mocker, @vitest/pretty-format, @vitest/runner, @vitest/snapshot, @vitest/spy, @vitest/utils
  • Peer deps: @vitest/browser-playwright, @vitest/browser-preview, @vitest/browser-webdriverio, @vitest/coverage-istanbul, @vitest/coverage-v8, @vitest/ui
• What changed in source: Per the compare metadata, the upstream fix adds concurrency limiting per task branch (using limitConcurrency wrapper) in packages/runner/src/run.ts — a bug fix to the test runner's concurrent task handling.
• Integrity hashes: All SHA512 integrity hashes updated correctly to new npm registry URLs.
• devDependency: Correctly marked as "dev": true throughout.

---

Standards Compliance

• ✅ No source code changes; only package-lock.json updated (auto-generated lockfile output)
• ✅ All @vitest/* subpackage versions kept in sync (all to 4.1.7)
• ✅ All peer dependency references updated to 4.1.7
• ✅ No breaking API changes in this patch (semver: patch version only)
• ✅ MIT license preserved on all packages

---

Linked Issue Fit

• No linked issue in PR body
• Release notes indicate fix for issue #10384: "Limit concurrency per task branch in addition to per leaf callbacks (backport)" — a runner concurrency bug fix
• The PR title correctly reflects a dependency update with a fix(deps): prefix

---

Evidence Provider Findings

N/A — No evidence providers configured.

---

Tool Harness Findings

N/A — No tool requests executed.

---

Unknowns / Needs Verification

• ⚠️ No package.json update in this PR: The repository scan shows package.json line 57 still declares "vitest": "^4.1.6". Renovate typically also updates package.json in the same PR, but this PR only contains package-lock.json. This may indicate:
  • The package.json will be updated in a follow-up commit after the lockfile converges
  • OR the repository's Renovate config pins vitest version separately
  • Action recommended: Verify that package.json is also updated to ^4.1.7 after this PR or merged separately. If not, request the package.json change be included.

---

Classification

Attribute	Value
Package	vitest monorepo
Change type	Dev dependency patch update
Risk level	Low
Breaking changes	None
Release type	Bug fix (concurrency runner fix)
Upstream quality	✅ Verified via GitHub compare metadata and release notes