build(deps): Bump vitest from 4.0.7 to 4.0.8 (#2823)

[KATO-Hiro]

close #2823

Summary by CodeRabbit

• Chores
  • Updated testing framework development tools to the latest patch versions for improved stability and compatibility.

[coderabbitai]

Walkthrough

Three vitest-related packages are updated in package.json from version 4.0.7 to 4.0.8: @vitest/coverage-v8, @vitest/ui, and vitest. No logic or control flow changes present.

Changes

Cohort / File(s)	Summary
Vitest dependency version bumps package.json	Bumped @vitest/coverage-v8, @vitest/ui, and vitest from 4.0.7 to 4.0.8

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

• Simple version bumps with no logic changes
• No modifications to exported entities or control flow

Poem

🐰 Hop, hop, hooray! Dependencies dance,
From point-seven up to point-eight, they prance,
Vitest grows stronger with each tiny leap,
The version machine keeps the upgrades sweet.
Carrots & code flow, forever they meet! 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title references bumping 'Vite' but the actual changes only bump @vitest packages, not Vite itself.	Update the title to accurately reflect the changes: 'build(deps): Bump vitest packages from 4.0.7 to 4.0.8' or similar.
Linked Issues check	❓ Inconclusive	The linked issue #2823 lacks specific coding requirements or objectives beyond the general dependency bump, making full compliance assessment impossible.	Verify that the dependency versions bumped match what was intended in issue #2823, and confirm no additional requirements were specified.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Out of Scope Changes check	✅ Passed	All changes are limited to version bumps in package.json for @vitest/coverage-v8, @vitest/ui, and vitest, which align with the stated objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch #2823

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Cache: Disabled due to data retention organization setting

Knowledge base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 1bea494 and dace7cd.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (1)

• package.json (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: preview

🔇 Additional comments (1)

package.json (1)

46-47: Consistent vitest ecosystem patch bump to v4.0.8.

All three related vitest packages are updated together from 4.0.7 to 4.0.8: @vitest/coverage-v8, @vitest/ui, and vitest. v4.0.8 is a patch release with bug fixes, published on Nov 7, 2025. This consistency across the ecosystem is appropriate, and the patch-level bump carries minimal risk.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[KATO-Hiro]

LGTM