Skip to content

chore(deps): update dependency vitest to v5 - #200

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 9, 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.11 → 5.0.1 age confidence

Reference


Release Notes

vitest-dev/vitest (vitest)

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
    • "before 7am every weekday"
  • 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 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.

@renovate
renovate Bot requested a review from a team as a code owner September 9, 2026 04:22
@renovate renovate Bot added the dependencies label Sep 9, 2026
@renovate
renovate Bot requested review from a team and Bloomca and removed request for a team September 9, 2026 04:22
@renovate renovate Bot added the dependencies label Sep 9, 2026

@doistbot doistbot left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Routine Renovate major bump of vitest from 4.1.11 to 5.0.0, with matching lockfile changes and no application-code edits — the test suite only uses standard vitest APIs that remain supported in v5.

Few things worth tightening:

  • vitest 5 requires Node ^22.12.0 || ^24.0.0 || >=26.0.0, but engines.node is still >=22.0.0. Since .npmrc sets engine-strict=true, contributors on Node 22.0–22.11 will hit a hard npm ci failure despite the manifest advertising their version — bump the floor to >=22.12.0.

Share Feedback • Review Logs

Comment thread package.json Outdated
"tsx": "4.23.13",
"typescript": "7.0.2",
"vitest": "4.1.11"
"vitest": "5.0.0"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

P2 vitest@5.0.0 requires Node ^22.12.0 || ^24.0.0 || >=26.0.0, but engines.node is still >=22.0.0. With engine-strict=true in .npmrc, contributors on Node 22.0–22.11 will get a hard npm ci failure even though the manifest says their version is supported. Bump the engines floor to >=22.12.0.

@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch 2 times, most recently from 9561c70 to f1c218d Compare September 16, 2026 03:20
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from f1c218d to 6b9a213 Compare September 21, 2026 03:43
@renovate
renovate Bot force-pushed the renovate/major-vitest-monorepo branch from 6b9a213 to 3546dd5 Compare September 25, 2026 00:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant