Skip to content

Update dependency vitest to v5 - #410

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

Update dependency vitest to v5#410
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@renovate

@renovate renovate Bot commented Sep 11, 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 (source) ^4.1.10^5.0.0 age confidence

Release Notes

vitest-dev/vitest (vitest)

v5.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

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

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

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

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


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

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

@coderabbitai

coderabbitai Bot commented Sep 11, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 7e981aab-8d4f-489c-8b3a-9061af74fbf2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Comment on lines 13 to 17
"devDependencies": {
"@cloudflare/vitest-pool-workers": "^0.22.0",
"vitest": "^4.1.10",
"vitest": "^5.0.0",
"wrangler": "^4.124.0"
}

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This bumps the worker's vitest to ^5.0.0 independently of vite-plus, which is exactly the anti-pattern CLAUDE.md documents:

The worker's vitest is coupled to vite-plus, and Renovate does NOT know it ... vite-plus pins the whole @vitest/* family at its own version (0.2.9 carries 4.1.10, 0.3.0 carries 4.1.11), so the worker's vitest has to move with vite-plus rather than ahead of it.

Here it's not just a minor bump ahead — it's a full major jump, and the resulting lockfile shows the exact breakage that note warns pnpm peers check should catch:

  • @cloudflare/vitest-pool-workers@0.22.0 declares peerDependencies: vitest: ^4.1.0, but this diff resolves it against vitest@5.0.0 — an unmet peer.
  • That same pool-workers snapshot still resolves @vitest/runner@4.1.11 / @vitest/snapshot@4.1.11, while the new vitest@5.0.0 snapshot has dropped those packages from its own dependency list entirely (inlined internally) — a cross-major internals mismatch in a single resolution graph.
  • vitest@5.0.0's own package entry declares an exact peer @vitest/browser-preview: 5.0.0, but the resolved optional dependency in this diff is @vitest/browser-preview@4.1.11(...)(vitest@4.1.11).

Per CLAUDE.md this bump should not land until vite-plus itself ships vitest 5 support, so the worker's vitest can move together with it rather than ahead of it.

@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from c621278 to e3b2fd8 Compare September 11, 2026 15:52
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from e3b2fd8 to 830e9f3 Compare September 11, 2026 16:07
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.

0 participants