Skip to content

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

Open
SamuelIVX wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo
Open

chore(deps): update dependency vitest to v5#251
SamuelIVX wants to merge 1 commit into
mainfrom
renovate/major-vitest-monorepo

Conversation

@SamuelIVX

@SamuelIVX SamuelIVX commented Sep 3, 2026 •
edited
Loading

Copy link
Copy Markdown
Owner

ℹ️ 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

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

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone America/New_York)

  • Branch creation
    • "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 has been generated by Mend Renovate CLI.

@github-actions github-actions Bot added the size/M label Sep 3, 2026
@github-actions

github-actions Bot commented Sep 3, 2026

Copy link
Copy Markdown

⚠️ Deprecation Warning: The deny-licenses option is deprecated for possible removal in the next major release. For more information, see issue 997.

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
npm/@vitest/mocker 5.0.0 UnknownUnknown
npm/@vitest/spy 5.0.0 UnknownUnknown
npm/magic-string 1.2.3 🟢 4.5
Details
CheckScoreReason
Packaging⚠️ -1packaging workflow not detected
Maintained🟢 1027 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Code-Review🟢 7Found 21/30 approved changesets -- score normalized to 7
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Binary-Artifacts🟢 10no binaries found in the repo
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Security-Policy⚠️ 0security policy file not detected
License🟢 10license file detected
Fuzzing⚠️ 0project is not fuzzed
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
npm/tinybench 6.1.4 UnknownUnknown
npm/vitest 5.0.0 UnknownUnknown

Scanned Files

  • package-lock.json

@coderabbitai

coderabbitai Bot commented Sep 3, 2026 •
edited
Loading

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Team

Run ID: 2d3802d3-d263-44d2-a655-26abb1d45cd0

📥 Commits

Reviewing files that changed from the base of the PR and between 4c8599e and 9413d36.

⛔ Files ignored due to path filters (1)
  • package-lock.json is excluded by !**/package-lock.json
📒 Files selected for processing (1)
  • package.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

📜 Recent review details
🔇 Additional comments (1)
package.json (1)

49-49: 🎯 Functional Correctness

No compatibility change is required. The manifest selects Vite ^7.0.0, the lockfile resolves Vite 7.3.6, and CI uses Node.js 24; these satisfy Vitest 5 requirements.

📝 Summary

Summary by CodeRabbit

  • Chores
    • Updated the testing tool used during development to a newer major version.

Walkthrough

The pull request updates the vitest development dependency in package.json from ^4.1.10 to ^5.0.0.

Changes

Vitest version update

Layer / File(s) Summary
Update Vitest development dependency
package.json		 The vitest development dependency changes from ^4.1.10 to ^5.0.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 9413d

This updates the test framework dependency to Vitest 5 without an identified current compatibility or runtime issue. The change is ready to merge after normal dependency checks.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Title check ✅ Passed The title clearly and concisely describes the main change: updating the Vitest dependency to version 5.
Description check ✅ Passed The description is directly related to the dependency update and includes the version change, release notes, breaking changes, and Renovate details.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/major-vitest-monorepo

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies size/M

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@SamuelIVX