chore(deps-dev): bump @vitest/browser-playwright from 4.1.11 to 5.0.0

[dependabot]

Bumps @vitest/browser-playwright from 4.1.11 to 5.0.0.

Release notes

Sourced from @​vitest/browser-playwright's releases.

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

• Replace loupe.inspect with pretty-format  -  by @​hi-ogawa, Claude Opus 5 (1M context) and OpenAI Codex in vitest-dev/vitest#9609 (3f802)
• Remove quotes from string values in test.for/each title $ variable (take 2)  -  by @​hi-ogawa in vitest-dev/vitest#10170 (04d37)
• Default attachmentsDir from .vitest-attachements/ to .vitest/attachments/  -  by @​MdSadiqMd in vitest-dev/vitest#10186 (1ba73)
• Remove sequential test/suite options in favor of concurrent  -  by @​hi-ogawa and OpenAI Codex in vitest-dev/vitest#10198 (9229f)
• Represent locator as an object instead of a string  -  by @​sheremet-va in vitest-dev/vitest#10212 (80f07)
• Inline expect package  -  by @​sheremet-va in vitest-dev/vitest#10221 (ad162)
• Remove deprecated entry points  -  by @​sheremet-va in vitest-dev/vitest#10222 (994c6)
• Require Node.js 22 and Vite 6.4  -  by @​sheremet-va in vitest-dev/vitest#10178 (38762)
• Fail expect.poll when function didn't resolve in time  -  by @​hi-ogawa and OpenAI Codex in vitest-dev/vitest#10233 (4df04)
• Throw an error if hoistable methods are outside the top level scope  -  by @​sheremet-va in vitest-dev/vitest#10460 (d0b4f)
• toHaveTextContent is strict, add toMatchTextContent as alternative  -  by @​sheremet-va in vitest-dev/vitest#10473 (18f30)
• Don't lookup config file from ancestor directories  -  by @​hi-ogawa, OpenAI Codex and Hiroshi Ogawa in vitest-dev/vitest#10428 (945d9)
• Inline @vitest/runner package, do not publish it anymore  -  by @​sheremet-va in vitest-dev/vitest#10511 (6d6e4)
• Allow mutating happy-dom/jsdom window object  -  by @​hi-ogawa, Hiroshi Ogawa and OpenAI Codex in vitest-dev/vitest#10373 (206e8)
• Expose concurrencyId/workerId on TestModule's diagnostics, make id 1-based  -  by @​sheremet-va in vitest-dev/vitest#10516 (bdd98)
• Add screenshotDirectory config to browser.expect.toMatchScreenshot  -  by @​macarie in vitest-dev/vitest#10592 (a60de)
• Update @sinonjs/fake-timers and support mocking Temporal  -  by @​hi-ogawa, Hiroshi Ogawa and OpenCode (gpt-5.6-sol) in vitest-dev/vitest#10654 (f8b15)
• Remove webdriverio package  -  by @​sheremet-va in vitest-dev/vitest#10675 (5fed6)
• Clear mocks by default before each test  -  by @​sheremet-va in vitest-dev/vitest#10613 (0f646)
• Don't emit localStorage warnings on Node 26, fail gracefully when worker fails to start  -  by @​sheremet-va in vitest-dev/vitest#10293 (334ed)
• Separate config resolution from the server creation  -  by @​sheremet-va in vitest-dev/vitest#10554 (1c0ec)
• Inline projects extend the root config by default  -  by @​sheremet-va in vitest-dev/vitest#10750 (fec00)
• Enable mocking Temporal without fake timers  -  by @​fabon-f, Hiroshi Ogawa and OpenCode (gpt-5.6-sol) in vitest-dev/vitest#10757 (ac2d4)
• Support nested projects  -  by @​sheremet-va in vitest-dev/vitest#10846 (ec367)
• Use > as separator in -t, calculate only once  -  by @​sheremet-va in vitest-dev/vitest#10686 (a0b20)
• Fail the test when an asynchronous assertion is not awaited  -  by @​sheremet-va in vitest-dev/vitest#10868 (86d4a)
• Share the Vite server between inline projects  -  by @​sheremet-va in vitest-dev/vitest#10848 (d87c9)
• Parse files statically in vitest list by default  -  by @​sheremet-va in vitest-dev/vitest#11088 (51e94)
• benchmark:
  • Rewrite the public API  -  by @​sheremet-va in vitest-dev/vitest#10113 (19f6e)
• browser:
  • Iframe scale  -  by @​macarie in vitest-dev/vitest#9745 (b6398)
  • Enable locators.exact by default  -  by @​sheremet-va in vitest-dev/vitest#10430 (e2032)
  • Require sessionId for orchestrator html request  -  by @​hi-ogawa, Hiroshi Ogawa and OpenAI Codex in vitest-dev/vitest#10522 (79b7d)
  • Save failure screenshots in attachmentsDir  -  by @​macarie in vitest-dev/vitest#10917 (3b5bb)
• coverage:
  • include/exclude globs too eager  -  by @​AriPerkkio in vitest-dev/vitest#9818 (edacb)
  • Allow thresholds.perFile to accept an object  -  by @​vladlenskiy and @​AriPerkkio in vitest-dev/vitest#10190 (13b78)
• expect:
  • Fix toThrow("") behavior by reverting #6710  -  by @​hi-ogawa in vitest-dev/vitest#9643 and vitest-dev/vitest#6710 (6c3e4)
• mocker:
  • Deserialize automock as automock  -  by @​nami8824 in vitest-dev/vitest#10192 (2f892)
• reporters:
  • blob reporter and --merge-reports default to .vitest/blob/  -  by @​AriPerkkio in vitest-dev/vitest#10232 (d22b0)
  • Write json and junit reporter output files to .vitest by default  -  by @​hi-ogawa, Hiroshi Ogawa, OpenCode (gpt-5.6-sol) and @​AriPerkkio in vitest-dev/vitest#10621 (58577)

... (truncated)

Commits

• f441c6f chore: release v5.0.0 (#11130)
• 897f51f chore: release v5.0.0-rc.4 (#11107)
• dc10f5f fix(browser): report the action error when a task times out (#11101)
• 7db80dc chore: release v5.0.0-rc.3 (#11089)
• af83d1b chore: release v5.0.0-rc.2 (#10976)
• c496c2e fix(browser): fail instead of hanging when the browser stops responding (#10956)
• 032d318 fix(browser): trigger playwright/chromium gc on lower disk availability (#10912)
• a7fa111 chore: release v5.0.0-rc.1 (#10920)
• 0553851 chore: add Knip checks (#10847)
• b7be731 chore: release v5.0.0-beta.7 (#10825)
• Additional commits viewable in compare view

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9559571

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

🤖 Bip Bop - Automated Dependency review of @vitest/browser-playwright@5.0.0

Note

Model: gpt-5.6-luna
Reviewed commit: 9425ee863a80
Workflow: View research run

🟡 Verdict: HOLD

Confidence: high

Readiness: needs changes

The provider-only upgrade is technically incompatible: @vitest/browser-playwright@5.0.0 requires Vitest 5, while the repository still resolves and declares Vitest 4.1.11. The missing coordinated Vitest upgrade and mandatory changesets are blockers; pending CI and approval are separate readiness gates.

Key findings

• Major update: 4.1.11 → 5.0.0 (PR diff).
• Compatibility blocker: v5 declares vitest: 5.0.0 as a peer, but the lockfile retains vitest@4.1.11 (v5 metadata, lockfile resolution).
• Active usage: Repository configs and the published React test plugin directly call playwright(), so provider behavior is enabled by default rather than opted out (provider wiring, dev portal config).
• Upstream breaking changes: Vitest 5 changes locator strictness, removes deprecated entry points, requires Node 22/Vite 6.4, and changes several test APIs (release notes, Vitest 5 migration guide).
• Security: No target-version security issue was identified; the blocking risk is compatibility.
• CI evidence: Current Unit tests, Build affected packages, Code quality, and Playwright jobs are still in progress (checks). Completed checks validate agent-context consistency and labeling, not Vitest 5 compatibility. Browser tests do not cover all Vitest 5 API/default changes or downstream consumer installation.
• Prior failure evidence: An earlier Unit tests run reported a Vitest 4/5 module mismatch involving BrowserConnectionError (failed Unit tests logs).
• Discussion and review: No unresolved review threads are present, but the PR has no approving review and Dependabot reports no changeset (PR discussion, repository ruleset).
• Branch freshness: GitHub compare reports behind_by: 3 and ahead_by: 1 against the current main head (compare API). The ruleset does not require strict up-to-date branches, so rebasing is optional unless conflicts emerge.

Repository impact

The update affects five published packages and six versioned cookbooks, plus their lockfile entries. The published Vitest React plugin still declares Vitest 4-compatible peer ranges, so accepting this provider alone would leave both internal and downstream test environments with mismatched Vitest majors (plugin manifest, Dependabot policy).

Merge path

• Choose and implement one compatible strategy: upgrade the coordinated Vitest packages and peer ranges to v5, or keep @vitest/browser-playwright on the Vitest 4-compatible line.
• Add changesets for every affected published package and cookbook, as required by repository policy.
• Re-run the required Unit tests, build, and code-quality checks; resolve compatibility failures.
• Obtain one required approving review and confirm all required checks pass with no unresolved threads.
• Optional hardening: add targeted tests for Vitest 5 browser-provider defaults and published-package consumer installation.

Generated by Fusion AI using the repository dependency-review skill.

[dependabot]

Superseded by #5575.