build(deps): Bump vitest from 4.0.8 to 4.0.13 (#2875)

[KATO-Hiro]

close #2875

Summary by CodeRabbit

• Chores
  • Updated testing framework dependencies to newer versions for improved stability and performance.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Updated vitest and related development dependencies from version 4.0.8 to 4.0.13 in package.json. Changes affect @vitest/coverage-v8, @vitest/ui, and vitest packages across devDependencies and dependencies. No functional code modifications.

Changes

Cohort / File(s)	Summary
Dependency Version Bumps package.json	Updated @vitest/coverage-v8, @vitest/ui, and vitest from 4.0.8 to 4.0.13

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A hop, a skip, through versions we go,
Vitest bumped up, patch by patch it will flow,
From 4.0.8 to 4.0.13 so neat,
Dependencies dancing—the update's complete! ✨

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: bumping vitest dependency versions from 4.0.8 to 4.0.13.
Linked Issues check	✅ Passed	The pull request successfully addresses the linked issue #2875 by updating vitest versions from 4.0.8 to 4.0.13 as required.
Out of Scope Changes check	✅ Passed	All changes are scoped to dependency version updates in package.json; no unrelated code modifications or out-of-scope changes are present.
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 #2875

---

📜 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 537b427 and 4498b3f.

⛔ 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 and compatible patch version bump.

vitest 4.0.13 was released on November 21, 2025, and includes fixes such as "types: Don't use type from Vite 7.1". This is particularly beneficial since the project uses Vite 7.2.4 (line 69). All three vitest-related packages are consistently updated to 4.0.13, and this patch version bump carries no breaking changes within the 4.0.x line.

Also applies to: 70-70

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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