You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
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
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @vitest/browser-playwright from 4.1.11 to 5.0.1.
Release notes
Sourced from @vitest/browser-playwright's releases.
... (truncated)
Commits
03630a5chore: release v5.0.1 (#11275)f441c6fchore: release v5.0.0 (#11130)897f51fchore: release v5.0.0-rc.4 (#11107)dc10f5ffix(browser): report the action error when a task times out (#11101)7db80dcchore: release v5.0.0-rc.3 (#11089)af83d1bchore: release v5.0.0-rc.2 (#10976)c496c2efix(browser): fail instead of hanging when the browser stops responding (#10956)032d318fix(browser): trigger playwright/chromium gc on lower disk availability (#10912)a7fa111chore: release v5.0.0-rc.1 (#10920)0553851chore: add Knip checks (#10847)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)