💥 Bump vitest from 3.0.0-beta to 3.2.4 (#2065)

[KATO-Hiro]

close #2065

Summary by CodeRabbit

• Chores
  • Updated development dependencies for Vitest and related packages to the latest stable versions.
  • Upgraded the specified package manager version for improved compatibility.

[coderabbitai]

Walkthrough

The package.json file was updated to upgrade the Vitest-related development dependencies from version 3.0.0-beta.3 to 3.2.4 and to update the pnpm package manager version from 10.2.1 to 10.12.1. No other changes were made.

Changes

File	Change Summary
package.json	Upgraded @vitest/coverage-v8, @vitest/ui, and vitest from 3.0.0-beta.3 to 3.2.4; updated pnpm version to 10.12.1

Assessment against linked issues

Objective	Addressed	Explanation
Upgrade Vitest-related dependencies to 3.x (including @vitest/coverage-v8, @vitest/ui, vitest) (#2065)	✅
Update package manager version to latest compatible pnpm (#2065)	✅
Review changelog and breaking changes, fix if needed (#2065)	❓	Only dependency versions were updated; no code changes to address breakages are present.
Ensure existing tests pass (#2065)	❓	No evidence in this change that test execution or results were verified.

Poem

A hop and a skip, dependencies rise,
Vitest is fresh, with stable new ties.
Pnpm’s grown, the carrots are sweet,
Our testing burrow is now up-to-date and neat.
🥕✨
— A jubilant rabbit in the code garden

---

📜 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 2cb95c1 and 164c67d.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build (22.x)

🔇 Additional comments (3)

package.json (3)

45-46: Align Vitest plugin versions The @vitest/coverage-v8 and @vitest/ui packages have been bumped to 3.2.4, matching the core release.

---

69-69: Upgrade Vitest core The vitest dependency is now 3.2.4. Please verify that any custom configuration or plugin usage is still compatible with this stable release.

---

98-98: Update pnpm version The packageManager field has been updated to [email protected]. Ensure your CI and local environments are using this version to prevent lockfile or workflow inconsistencies.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[KATO-Hiro]

LGTM