Skip to content

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

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest/browser-playwright-5.0.1
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest/browser-playwright-5.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 18, 2026

Copy link
Copy Markdown
Contributor

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

Release notes

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

v5.0.1

   🚀 Features

   🐞 Bug Fixes

    View changes on GitHub

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

... (truncated)

Commits

Dependabot compatibility score

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)

Bumps [@vitest/browser-playwright](https://github.com/vitest-dev/vitest/tree/HEAD/packages/browser-playwright) from 4.1.11 to 5.0.1.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.1/packages/browser-playwright)

---
updated-dependencies:
- dependency-name: "@vitest/browser-playwright"
  dependency-version: 5.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 18, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner September 18, 2026 17:11
@changeset-bot

changeset-bot Bot commented Sep 18, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 8b79534

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

Copy link
Copy Markdown
Contributor

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

Note

Model: gpt-5.6-luna
Reviewed commit: 8b79534674fe
Workflow: View research run

🟡 Verdict: HOLD

Confidence: high

Readiness: needs changes

The update is not technically compatible as submitted: @vitest/browser-playwright@5.0.1 requires vitest@5.0.1, while every affected package still declares Vitest 4.x. The branch is mergeable and current, but the required compatibility decision and changesets are missing.

Key findings

  • Technical verdict — HOLD: The target package’s peer contract changed from Vitest 4.1.11 to exact Vitest 5.0.1 (4.1.11 metadata, 5.0.1 metadata). The PR changes only @vitest/browser-playwright to 5.0.1; affected packages continue using Vitest ^4.1.x (PR manifest diff).
  • Direct repository usage is active in vitest.config.ts files through playwright() and in packages/vitest-plugin/react-app/src/define-project.ts; these call sites do not explicitly opt out of Vitest 5 browser behavior (roles config, shared project config).
  • Vitest 5 is a semver-major release with documented breaking changes, including locator representation and removed/deprecated APIs (Vitest 5 announcement, PR release notes).
  • Security — clear: No security-specific behavior or production dependency is changed; the update is confined to development/browser-test tooling.
  • Validation: At review time, Verify agent context is in sync and Auto-Label PRs passed. Unit tests, affected-package builds, code quality, and Playwright checks were still running (PR checks). CodeQL was neutral because its default configuration was unavailable, not because a vulnerability was reported (CodeQL run).
  • Confidence is high: the peer-version conflict is explicit in package metadata and consistent with repository manifests and active provider call sites.

Repository impact

  • The update affects six cookbook packages and five published packages, including @equinor/fusion-framework-dev-portal, @equinor/fusion-framework-react-app, @equinor/fusion-framework-react-components-roles, @equinor/fusion-observable, and @equinor/fusion-framework-vitest-plugin-react-app (changed files).
  • Under repository policy, changesets are mandatory for @equinor/fusion-framework-dev-portal and all changed cookbooks/* packages. The changeset bot reports none (changeset policy, PR discussion).
  • No unresolved review comments or submitted approvals were found. The active main ruleset requires one approval, required thread resolution, code quality success, and CodeQL thresholds (main ruleset).
  • The branch is mergeable and 0 commits behind current main; freshness is not a blocker (compare API, PR status).

Merge path

  • Resolve the peer compatibility decision: upgrade the affected Vitest declarations and validate Vitest 5 migration impact, or keep @vitest/browser-playwright on a Vitest-4-compatible release.
  • Add the seven policy-required changesets: @equinor/fusion-framework-dev-portal plus the six changed cookbook packages.
  • Complete required unit-test, build, code-quality, and Playwright checks; inspect any failures rather than attributing them to the dependency from workflow names.
  • Obtain the required approving review and ensure required review threads are resolved.
  • Recheck mergeability; rebasing is optional because behind_by=0 and no conflict is reported.

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

@github-actions github-actions Bot added the 🤖 AI researched Dependency research completed by the Fusion AI workflow label Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🤖 AI researched Dependency research completed by the Fusion AI workflow 🚧 chore maintaines work, (update deps, workflos ...) 👨🏻‍🍳 cookbooks dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code 👾 React 🛠️ utils packages related to utils

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants