chore(deps): update vitest to v5 - #537
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Team Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (18)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe monorepo upgrades Vitest to version 5. Benchmark files adopt the test-scoped benchmark API. Browser tests update text matching, link queries, hover interactions, and tag-label expectations. ChangesVitest 5 migration
Estimated code review effort: 3 (Moderate) | ~25 minutes Merge Risk: 🟡 Moderate · up to This updates the test platform to Vitest 5, but browser-test adapter compatibility remains unresolved and may cause intermittent test failures. The change should wait for the upstream compatibility blocker to be addressed or explicitly accepted. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 11 files. (7 skipped: 7 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
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. Comment |
commit: |
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Moves the test stack to Vitest 5:
benchis now a test-context fixture, partial text assertions move totoMatchTextContent, text locators that target visible text sitting next to the hidden Markdown syntax kept in the DOM pass{ exact: false }now thatbrowser.locators.exactdefaults totrue, and the code block toolbar tests hover before clicking to satisfy the new actionability check.vitest-browser-react@2.2.0still declares avitest: ^4peer, sopnpm-workspace.yamlallows v5 for it until a wider range ships.Heads-up: the hover-driven
link-menu.test.tsxtests flake under v5 (3 of 10 local runs red, 0 of 10 on v4); CI retries absorb it, but it is worth a follow-up.Blocking by vitest-community/vitest-browser-react#63
Summary by CodeRabbit
Tests
Chores