chore(dependencies): update vitest and @vitest/ui versions to v3

[gweesin]

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: #3085

What is the new behavior?

bump vitest v3 and use --ui argument correctly.

Does this PR introduce a breaking change?

• Yes
• No

Other information

https://vitest.dev/guide/migration.html#vitest-3

Summary by CodeRabbit

• Chores
  • Updated testing dependencies by shifting the resolution method for a key UI testing package across our Vue examples.
  • Upgraded the core testing tool to a new major version and added a corresponding UI package for enhanced testing integration.

[coderabbitai]

Walkthrough

This change updates dependency management configurations across example projects. In both the Vue 2 and Vue 3 examples, the @vitest/ui dependency has its version specification changed from "^0.31.0" to "catalog:" in their respective package.json files (with a minor formatting update in Vue 3). In addition, the pnpm-workspace.yaml file upgrades the vitest version from "^2.1.8" to "^3.0.8" and adds @vitest/ui with version "^3.0.8".

Changes

File(s)	Change Summary
examples/vue2/package.json, examples/vue3/package.json	Updated @vitest/ui in devDependencies from "^0.31.0" to "catalog:". The Vue 3 file also includes a newline formatting change at the end of the file.
pnpm-workspace.yaml	Upgraded vitest from "^2.1.8" to "^3.0.8" and added a new catalog entry for @vitest/ui with version "^3.0.8".

Possibly related PRs

• build(dts): fix dts error when build vue2 components #2606: Updates similar dependency version specifications using a catalog reference for @vitest/ui in package configuration files.
• feat: [grid,alert,form]use catalog to globally upgrade vite and vitest; and add mobile build config #2680: Modifies the version specification of @vitest/ui across multiple package.json files.

Suggested labels

chore, enhancement

Suggested reviewers

• zzcr

Poem

I'm a little code rabbit, hopping through the night,
Updating versions with a joyful byte.
Dependencies shifted like a gentle breeze,
From caret hints to catalog keys.
With whiskered cheer, I nimbly dance—
Cheers to changes that give code a chance!
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between cd468ac and 93f6c52.

📒 Files selected for processing (3)

• examples/vue2/package.json (2 hunks)
• examples/vue3/package.json (2 hunks)
• pnpm-workspace.yaml (1 hunks)

🔇 Additional comments (4)

pnpm-workspace.yaml (1)

7-9: Updated Vitest and @vitest/ui Versions in Catalog.
The catalog now specifies 'vitest': '^3.0.8' and '@vitest/ui': '^3.0.8', which is consistent with the PR’s objective of migrating to Vitest v3. Please verify that these catalog entries correctly influence dependency resolution in all workspace packages.

examples/vue2/package.json (1)

35-35: Update @vitest/ui Dependency to Catalog Reference.
Changing the version from "^0.31.0" to "catalog:" ensures that the dependency is now resolved based on the unified version provided in the workspace catalog, aligning with the overall upgrade strategy.

examples/vue3/package.json (2)

40-40: Updated @vitest/ui Dependency Version to Catalog Reference.
The modification to "@vitest/ui": "catalog:" guarantees consistency with the version specified in the workspace catalog, which supports the migration to Vitest v3.

---

61-62: Minor Formatting Improvement.
The addition of a newline after the closing brace improves consistency and readability of the JSON file.

---

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.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate unit testing code.
  • @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.

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 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.

[petercat-assistant]

Walkthrough

This pull request updates the versions of vitest and @vitest/ui to version 3.0.8 in the pnpm-workspace.yaml file. It also updates the package.json files for both Vue 2 and Vue 3 examples to reflect these changes. The update ensures the correct usage of the --ui argument as per the new version's requirements.

Changes

File	Summary
examples/vue2/package.json, examples/vue3/package.json	Updated vitest and @vitest/ui versions to ^3.0.8.
pnpm-workspace.yaml	Updated vitest and added @vitest/ui with version ^3.0.8.

[petercat-assistant]

Ensure that all dependencies are compatible with vitest version 3.0.8, as this is a major version update and may introduce breaking changes.

[github-actions]

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide