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
Fix importOriginal with optimizer and query import [backport to v4] - by Hiroshi Ogawa, David Harris, Codexand Vladimir in vitest-dev/vitest#10546(a5180)
browser:
Wait for orchestrator readiness before resolving browser sessions [backport to v4] - by Vladimir and Séamus O'Connor in vitest-dev/vitest#10555(7fb29)
Hoist vi.mock() for vite-plus/test imports [backport to v4] - by Hiroshi Ogawa, LongYinan, Claude Opus 4.8 and Vladimir in vitest-dev/vitest#10548(2c955)
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
test (devDependency of @equinor/fusion-framework-module-event)
Manifest change is limited to packages/modules/event/package.json: "vitest": "^3.2.7" → "^4.1.11".
Findings
Upstream changes: Vitest 4 is a major line with a reworked browser mode, changed default reporters, updated snapshot/spy semantics, and removal of several v3 deprecations.
Breaking changes: Vitest 4 does contain documented breaking changes relative to v3. However, the rest of this monorepo already runs Vitest 4 — the workspace root declares "vitest": "^4.1.10" and the installed root resolution is already 4.1.11. This PR therefore aligns the last remaining v3 holdout rather than performing a v3→v4 migration, which materially reduces the practical risk.
Security: No GitHub advisories affecting vitest@4.1.11. Package is not deprecated.
Release age: 4.1.11 published 2026-08-18T14:27Z — approximately 328 hours old, well past the 48-hour threshold.
Affected packages: @equinor/fusion-framework-module-event only, and only in devDependencies. Test tooling is not part of the package's published output.
Validation signal: the full suite is green on the rebased branch (182 test files / 1358 tests, 88/88 build tasks, Biome clean).
Executed as the required sequence pnpm test && pnpm build && pnpm -w check (exit 0).
Changesets
Package
Bump
File
@equinor/fusion-framework-module-event
none
not required
vitest is a devDependency and test tooling only — it does not affect the published output of @equinor/fusion-framework-module-event. This matches the documented skip rule for devDependency changes in non-cookbook packages.
Assessment
Security: clear - No advisories affect vitest@4.1.11; not deprecated; release is ~328 hours old.
Compatibility: concern - This is a major version bump (3.x → 4.x). Mitigating context: the workspace root and every other package already run Vitest ^4.1.10, so this only aligns the last v3 holdout, and the full suite passes.
Impact: clear - Scoped to one package's devDependencies; no published runtime surface is affected.
Next Step
Awaiting manual review because this is a major version bump. The batch policy in .github/instructions/dependabot-pr.instructions.md classifies any major bump as low confidence and explicitly forbids auto-merging it, so this PR was not merged despite fully green validation.
Recommendation for a maintainer: this is a low-risk major in practice — it is a version-alignment catch-up to the Vitest 4 line the rest of the monorepo already uses, and validation is green. A maintainer can merge it after a quick confirmation that no v3-specific test APIs remain in packages/modules/event.
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
🚧 choremaintaines work, (update deps, workflos ...)dependenciesPull requests that update a dependency filejavascriptPull requests that update Javascript code🧬 Modules
1 participant
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 from 3.2.7 to 4.1.11.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
9bd8d46chore: release v4.1.11 (#10995)9851dbcfix(browser): trigger playwright/chromium gc on lower disk availability [back...db616d2chore: release v4.1.10 (#10718)bae52b5fix(vm): fix external module resolve error with deps optimizer query for enco...a7a61e7chore: release v4.1.9 (#10598)934b0f5fix(pool): prevent test run hang on worker crash (#10543) [backport to v4] (#...7fb2965fix(browser): wait for orchestrator readiness before resolving browser sessio...a518019fix: fiximportOriginalwith optimizer and query import [backport to v4] (#...e61f2ddchore: release v4.1.8e4067b3fix(browser): disable clientcdpAPI whenallowWrite/allowExec: false[ba...