Fix: lock vitest version in CI

[nicktrn]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: dfb440a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

The changes update the GitHub Actions workflow files responsible for running unit tests and merging test reports. Specifically, the command used to merge test reports is modified to explicitly specify the use of Vitest version 3.1.4 by updating pnpm dlx vitest run --merge-reports to pnpm dlx vitest@3.1.4 run --merge-reports across multiple workflow files. No other workflow steps or logic are altered, and there are no changes to any exported or public entities.

---

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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (3)

.github/workflows/unit-tests-packages.yml (1)

130-130: Lock Vitest version to 3.1.4 for report merging.
Pinning this version ensures consistent CI report merging. Please verify it matches the version in your devDependencies (package.json) and consider centralizing the Vitest version as a workflow input or shared variable to avoid duplication across multiple workflows.

.github/workflows/unit-tests-internal.yml (1)

130-130: Lock Vitest version to 3.1.4 for report merging.
Consistent with other test workflows, pinning Vitest improves reproducibility. Double-check that this locked version matches your devDependencies and think about extracting it to a single reusable parameter to simplify future updates.

.github/workflows/unit-tests-webapp.yml (1)

136-136: Lock Vitest version to 3.1.4 for report merging.
Aligning this change with the other CI workflows helps maintain consistency. Please confirm the locked version matches your project’s vitest dependency and evaluate moving this value into a shared workflow input to reduce maintenance overhead.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 26b0523 and dfb440a.

📒 Files selected for processing (3)

• .github/workflows/unit-tests-internal.yml (1 hunks)
• .github/workflows/unit-tests-packages.yml (1 hunks)
• .github/workflows/unit-tests-webapp.yml (1 hunks)