chore(deps-dev): bump vitest from 3.2.4 to 3.2.6

[dependabot]

Bumps vitest from 3.2.4 to 3.2.6.

Release notes

Sourced from vitest's releases.

v3.2.6

   🐞 Bug Fixes

• Pin last supported vite-node version  -  by @​sheremet-va (16f12)

    View changes on GitHub

v3.2.5

   🚀 Features

• api: Add allowWrite and allowExec options to api [backport to v3]  -  by @​hi-ogawa and Codex in vitest-dev/vitest#10445 (af88b)

   🐞 Bug Fixes

• browser: Disable client cdp API when allowWrite/allowExec: false [backport to v3]  -  by @​hi-ogawa and Codex in vitest-dev/vitest#10456 (385a1)

    View changes on GitHub

Commits

• b6d56f8 chore: release v3.2.6
• 16f120d fix: pin last supported vite-node version
• 2cbad0a chore: release v3.2.5
• 385a1ae fix(browser): disable client cdp API when allowWrite/allowExec: false [ba...
• af88b1f feat(api): add allowWrite and allowExec options to api [backport to v3]...
• See full diff in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for vitest since your current version.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: chore(deps-dev): bump vitest from 3.2.4 to 3.2.6
• Issue: None. The title is specific, clear, and accurately describes a dependency bump.
• Recommendation: No change needed.

---

❌ Commit Type

• Current body: No commit type checkbox is selected.
• Issue: The template requires exactly one commit type to be selected.
• Recommendation: Check one box, for example: - [x] chore - Maintenance/tooling.

---

❌ Risk Level

• Current body: No risk level checkbox is selected.
• Issue: Every PR must include exactly one risk label/selection, and it should match the PR body’s risk section.
• Recommendation: Select one risk level. For a Vitest dependency bump with lockfile updates, Low is the most appropriate choice unless you know this impacts runtime behavior.
• Advised risk level: low.

---

✅ What & Why

• Current: (Missing)
• Issue: This section is required and should briefly explain the dependency update.
• Recommendation: Add a short explanation such as: Updates Vitest from 3.2.4 to 3.2.6 to pick up upstream bug fixes and keep dev/test tooling current.

---

⚠️ Impact of Change

• The section is present in the template, but no content is provided.
• Recommendation:
  • Users: No direct user-facing impact; affects development/test tooling only.
  • Developers: Vitest version bump and lockfile refresh may slightly change local test behavior or diagnostics.
  • System: No production system impact; dependency graph and test runner packages updated.

---

⚠️ Test Plan

• Assessment: The PR is a dependency update and includes no unit or E2E test changes in the diff. That is acceptable only if you add a clear manual-testing explanation or note that automated tests are not applicable.
• Recommendation: Since this is a dev dependency bump, mark Manual testing completed and explain something like: No code changes; dependency/lockfile update only. Existing test suites were not modified. Alternatively, if this PR was validated by CI, mention the relevant test run.

---

✅ Contributors

• No contributors listed, which is acceptable.
• Recommendation: Optional; add credit if anyone contributed implementation or review input.

---

✅ Screenshots/Videos

• Not applicable for this dependency-only change.
• Recommendation: None needed.

---

Summary Table

Section	Status	Recommendation
Title	✅	No change needed
Commit Type	❌	Select exactly one, e.g. chore
Risk Level	❌	Select exactly one risk level, likely Low
What & Why	❌	Add a brief explanation of the Vitest bump
Impact of Change	⚠️	Fill in brief user/dev/system impact notes
Test Plan	⚠️	Add manual-testing or CI validation note
Contributors	✅	Optional
Screenshots/Videos	✅	Not applicable

---

This PR does not fully pass body-template compliance yet. Please update the missing required fields, especially Commit Type, Risk Level, and What & Why, then re-submit. The advised risk level is lower than anything suggesting medium/high impact: this is a low-risk dependency bump.

---

Last updated: Tue, 07 Jul 2026 18:17:07 GMT

[github-actions]

📊 Coverage Check

No source files changed in this PR.

[rllyy97]

Dependency Review: vitest 3.2.4 -> 4.1.0

Verdict: Needs companion package updates + test fixes

This is a major version bump with breaking changes. The PR only updates vitest but leaves companion packages at v3:

Issues found:

1. Version mismatch: @vitest/coverage-istanbul (3.2.4) and @vitest/ui (3.2.4) need to be updated to 4.x to match vitest 4.1.0. Running mixed versions causes errors.
2. Snapshot failures: 5 snapshot tests failing in addActionCard.spec.tsx - vitest 4.x may serialize snapshots differently
3. Chat test failures: @microsoft/logic-apps-chat:test:lib failing

vitest 4.x breaking changes to be aware of:

• basic reporter removed (use default with summary: false)
• Coverage options changed (coverage.all, coverage.extensions removed)
• Default exclude patterns changed (only node_modules and .git excluded by default)
• V8 coverage uses AST-based remapping

Fix needed: Bump @vitest/coverage-istanbul and @vitest/ui to 4.x, update vitest config if needed, update snapshots, and fix chat tests. Will push a fix.

[rllyy97]

@copilot resolve the merge conflicts in this pull request

[Copilot]

@copilot resolve the merge conflicts in this pull request

Done in c8d08c8: merged origin/main into this branch and resolved the merge conflicts (including pnpm-lock.yaml), then validated lockfile integrity and reran targeted tests.

[dependabot]

A newer version of vitest exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.

[rllyy97]

@dependabot rebase

[dependabot]

Looks like this PR has been edited by someone other than Dependabot. That means Dependabot can't rebase it - sorry!

If you're happy for Dependabot to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

[rllyy97]

@dependabot recreate