Skip to content

chore(deps): update vitest monorepo to v5 - #767

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo
Closed

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Sep 5, 2026 •

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@vitest/browser (source) ^4.1.6 → ^5.0.0 age confidence
@vitest/browser-playwright (source) ^4.1.4 → ^5.0.0 age confidence
@vitest/coverage-v8 (source) ^4.1.6 → ^5.0.0 age confidence
vitest (source) ^4.1.6 → ^5.0.0 age confidence

Release Notes

vitest-dev/vitest (@​vitest/browser)

v5.0.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v5.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.0

Compare Source

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
   🚀 Features
   🐞 Bug Fixes

❗ Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented Sep 5, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c8297c1

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

@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 3 times, most recently from b399100 to 44ac205 Compare September 9, 2026 17:46
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 65336fd to 472f1f3 Compare September 16, 2026 10:54
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 5 times, most recently from 51487c6 to 6b5fcfc Compare October 1, 2026 05:52
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from a1c25f9 to c1e22b6 Compare October 1, 2026 06:03
@unional

unional commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

Why CI is red: two separate problems

1. browserTestPreset() enables browser mode too late (fixed upstream in repobuddy/repobuddy#718)

code / verify fails with:

TypeError: The browser server was not initialized for the "sb:browser (chromium)" project. This is a bug in Vitest.

Vitest 5 sets up Browser Mode in its vitest:browser:loader plugin (enforce: 'pre'). That plugin reads test.browser.enabled in its config hook, before normal-phase plugins run. browserTestPreset() from @repobuddy/vitest (2.3.0 and 2.4.0) is a normal-phase plugin, so the loader never sees browser mode as enabled. repobuddy/repobuddy#718 moves the preset to the pre phase. With that change applied locally, the browser server starts and the stories run.

2. Storybook 10.x sets no viewport under Vitest 5 (upstream blocker)

With problem 1 fixed, 9 visual-snapshot tests fail, in show_source, show_doc_source, and with_story_card. The screenshots are 414×896, while the __vis__/linux baselines are 960×720.

@storybook/addon-vitest 10.6.0 and 10.6.1 set the viewport with await import('@vitest/browser/context'). In Vitest 5, only vitest/browser is a virtual module. @vitest/browser/context resolves to a stub that exports page = null, so setViewport() returns early and every story renders at Vitest's default viewport. I confirmed this by logging inside setViewport: page is null.

Recommendation

Hold this PR until repobuddy/repobuddy#718 is released and Storybook ships a 10.x release with Vitest 5 support. The other option is to alias @vitest/browser/context to vitest/browser in the browser project. That is a workaround, so I did not apply it.

main passes verify. This branch, rebased on main with the preset fix, fails only the 9 snapshot tests above.

@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 6 times, most recently from 33df042 to 2fde48c Compare October 2, 2026 18:55
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 2fde48c to c8297c1 Compare October 3, 2026 05:47
@unional

unional commented Oct 4, 2026

Copy link
Copy Markdown
Contributor

Held: storybook-addon-vis (peer vitest ^4) and @repobuddy/vitest 2.x (peer vitest ^4) do not support vitest 5 yet, so this repo stays on vitest v4. Renovate rule added (vitest and @vitest/* <5); lift when those peers allow v5.

@unional unional closed this Oct 4, 2026
@renovate

renovate Bot commented Oct 4, 2026

Copy link
Copy Markdown
Contributor Author

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate
renovate Bot deleted the renovate/major-vitest-monorepo branch October 4, 2026 23:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant