Skip to content

👷 Update vitest monorepo to v5 - #219

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

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

Conversation

@renovate

@renovate renovate Bot commented Sep 12, 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/coverage-v8 (source) 4.1.10 → 5.0.1 age confidence
@vitest/ui (source) 4.1.10 → 5.0.1 age confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-v8)

v5.0.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v5.0.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes

❗ Important

✂ PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • 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.

@renovate
renovate Bot requested a review from a team as a code owner September 12, 2026 05:06
@datadog-prod-us1-3

datadog-prod-us1-3 Bot commented Sep 12, 2026 •

Copy link
Copy Markdown

Pipelines

✨ Unblock PR with BitsAI

❌ Errors

Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 1 Pipeline job failed

DataDog/electron-sdk | unit — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 07f3a15 | Docs | View more details | Give us feedback!

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

PR Review — Score: 2.0 / 5

This Renovate PR cannot be merged as-is. It bumps @vitest/coverage-v8 and @vitest/ui to 5.0.0 but leaves the core vitest package at 4.1.10, producing a mixed-version install that breaks the unit/coverage pipeline. I would not approve until all vitest monorepo packages are aligned on v5 and the test suite runs cleanly.

Why 2.0: The diff introduces an internally inconsistent dependency set (v4 core + v5 satellite packages). Running yarn test:unit loads vitest@4.1.10 with @vitest/coverage-v8@5.0.0, emits a mixed-version warning, and throws AssertionError: coverageFilesDirectory is required across workers — so the stated goal of upgrading the vitest monorepo to v5 is not achieved.

Why not 5: The upgrade is incomplete and breaks dev tooling. Completing it will also require reviewing Vitest 5 breaking changes (e.g. Node.js 22 minimum, default mock clearing, config/reporter path changes) once vitest itself is bumped.


Findings

  • [Blocking] Incomplete vitest monorepo upgrade — @vitest/coverage-v8 and @vitest/ui are at 5.0.0 but vitest remains at 4.1.10, causing mixed-version errors and broken coverage collection.
  • [Minor] Vitest 5 breaking changes pending — After aligning versions, review Vitest 5 release notes for test-suite impact (mock clearing defaults, Node 22 requirement, reporter/output path changes).
Open in Web View Automation 

Sent by Cursor Automation: electron-sdk reviews

Comment thread package.json Outdated
"@types/node": "24.13.3",
"@vitest/coverage-v8": "4.1.10",
"@vitest/ui": "4.1.10",
"@vitest/coverage-v8": "5.0.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.

These satellite packages are bumped to 5.0.0, but the core vitest devDependency on line 142 is still pinned to 4.1.10. Yarn reports peer conflicts (vitest 4.1.10 does not satisfy what @vitest/coverage-v8 5.0.0 requests), and running yarn test:unit prints:

Loaded vitest@4.1.10 and @vitest/coverage-v8@5.0.0.
Running mixed versions is not supported and may lead into bugs

followed by AssertionError: coverageFilesDirectory is required from @vitest/coverage-v8.

Please bump vitest to 5.0.0 in the same change (and dedupe the lockfile) so all @vitest/* packages share one major version.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ccf6113078

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread package.json Outdated
Comment on lines +123 to +124
"@vitest/coverage-v8": "5.0.0",
"@vitest/ui": "5.0.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.

P1 Badge Keep the Vitest packages on the same major version

The runner remains pinned to vitest@4.1.10 at line 142, while both upgraded packages declare an exact vitest@5.0.0 peer dependency; conversely, Vitest 4 declares exact 4.1.10 peers for these packages. Yarn reports all three peer requirements as incorrectly met, and the CI unit command (vitest run --coverage) loads this unsupported Vitest 4 / coverage provider 5 combination. Upgrade vitest to 5.0.0 as part of this monorepo update (and address its breaking changes), or keep the provider/UI packages on 4.1.10.

Useful? React with 👍 / 👎.

@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from ccf6113 to 59a6800 Compare September 15, 2026 09:09
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 59a6800 to b79b63f Compare September 22, 2026 23:10
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from b79b63f to 07f3a15 Compare September 24, 2026 15:32
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