chore(deps-dev): bump vitest from 3.2.7 to 4.1.10

[ThePlenkov]

User description

Vitest 3.2.7 → 4.1.10. All 23 project test targets pass under Vitest 4.1.10.

Generated with Devin

---

CodeAnt-AI Description

Upgrade project testing to Vitest 4.1.10

What Changed

• All project test targets now use Vitest 4.1.10 instead of Vitest 3.x
• The shared test setup is aligned across the workspace packages
• Existing tests continue to pass with the upgraded test runner

Impact

✅ Consistent test execution across packages
✅ Tests remain compatible with the current toolchain

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

---

Summary by cubic

Upgrades vitest from 3.2.7 to 4.1.10 across all workspaces to align with Vite 7 and current peers. v3 allowed Vite 5 and @types/node 18; v4 requires Vite 6–8 and @types/node 20+. All 23 test targets pass.

Review notes

• Bumps vitest in the root and every package; updates bun.lock.
• Transitives: chai@6, es-module-lexer@^2, std-env@^4, tinyrainbow@^3.
• Keeps root typescript@5.x (rebased to drop incompatible TS 7).
• Migration: if you run tests with Vite 5 or @types/node 18 locally, upgrade to Vite 6+ and @types/node 20+.

^{Written for commit c809dd6. Summary will update on new commits.}

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	ceead21	Aug 18, 2026 · 12:40	12:41

[coderabbitai]

Warning

Review limit reached

@ThePlenkov, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 16 minutes

Limit details: You’ve used all 3 included reviews currently available under your plan.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: f19198a9-7138-465b-a8ad-54796ee13aa6

📥 Commits

Reviewing files that changed from the base of the PR and between 33054a3 and c809dd6.

⛔ Files ignored due to path filters (1)

• bun.lock is excluded by !**/*.lock

📒 Files selected for processing (24)

• package.json
• packages/cdk/package.json
• packages/checks/package.json
• packages/cli/package.json
• packages/compiler-earthly/package.json
• packages/compiler-github/package.json
• packages/compiler-gitlab/package.json
• packages/conformance/package.json
• packages/core/package.json
• packages/decorators/package.json
• packages/engine-native/package.json
• packages/findings/package.json
• packages/github/package.json
• packages/gitlab/package.json
• packages/ir/package.json
• packages/planner/package.json
• packages/plugin/package.json
• packages/policy/package.json
• packages/runtime-docker/package.json
• packages/runtime-host/package.json
• packages/runtime-podman/package.json
• packages/runtime-remote/package.json
• packages/runtime/package.json
• packages/sdk/package.json

---

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

[baz-reviewer]

Merger

Needs Review

Vitest’s major upgrade affects every workspace, but no CI run was recorded to verify the claimed 23 passing test targets.

_{Commit c809dd6 · Evaluated 2026-08-18 12:59 UTC}

_{Review this PR on Baz | Customize your next review}

[amazon-q-developer]

This PR cleanly upgrades Vitest from version 3.2.7 to 4.1.10 across all 23 project packages. The dependency updates are consistent and properly reflected in the lockfile. Since all test targets pass with the new version, this upgrade appears ready for merge.

---

You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric	Results
Complexity	0
Duplication	0

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[qodo-code-review]

PR Summary by Qodo

Upgrade Vitest to 4.1.10 across all workspaces

⚙️ Configuration changes 🕐 10-20 Minutes

AI Description

• Upgrades Vitest from 3.2.7 to 4.1.10 across all 23 test targets.
• Refreshes Bun's resolved dependency graph for the Vitest major release.
• Preserves passing tests across all project targets under Vitest 4.

Diagram

graph TD
  A["Root manifest"] --> B["Workspace manifests"] --> C["Bun resolver"] --> D["Bun lockfile"] --> E["Vitest 4"] --> F["Test targets"]

Loading

High-Level Assessment

The PR follows the repository's existing package-level dependency model and keeps every workspace on one Vitest major version. A root-only declaration would reduce duplication but could weaken package-level tooling and dependency clarity, so synchronized manifests plus a regenerated lockfile are appropriate.

Files changed (25) +64 / -82

Other (25) +64 / -82

bun.lockResolve the Vitest 4.1.10 dependency graph +40/-58

Resolve the Vitest 4.1.10 dependency graph

• Updates all root and workspace Vitest resolutions to 4.1.10. Refreshes Vitest packages and related transitive dependencies, including Chai, Standard Schema, source-map support, and environment utilities.

bun.lock

package.jsonPin root Vitest to 4.1.10 +1/-1

Pin root Vitest to 4.1.10

• Upgrades the root development dependency from Vitest 3.2.7 to 4.1.10.

package.json

package.jsonUpgrade CDK tests to Vitest 4 +1/-1

Upgrade CDK tests to Vitest 4

• Updates the CDK package's Vitest development dependency to ^4.1.10.

packages/cdk/package.json

package.jsonUpgrade checks tests to Vitest 4 +1/-1

Upgrade checks tests to Vitest 4

• Updates the checks package's Vitest development dependency to ^4.1.10.

packages/checks/package.json

package.jsonUpgrade CLI tests to Vitest 4 +1/-1

Upgrade CLI tests to Vitest 4

• Updates the CLI package's Vitest development dependency to ^4.1.10.

packages/cli/package.json

package.jsonUpgrade Earthly compiler tests to Vitest 4 +1/-1

Upgrade Earthly compiler tests to Vitest 4

• Updates the Earthly compiler package's Vitest development dependency to ^4.1.10.

packages/compiler-earthly/package.json

package.jsonUpgrade GitHub compiler tests to Vitest 4 +1/-1

Upgrade GitHub compiler tests to Vitest 4

• Updates the GitHub compiler package's Vitest development dependency to ^4.1.10.

packages/compiler-github/package.json

package.jsonUpgrade GitLab compiler tests to Vitest 4 +1/-1

Upgrade GitLab compiler tests to Vitest 4

• Updates the GitLab compiler package's Vitest development dependency to ^4.1.10.

packages/compiler-gitlab/package.json

package.jsonUpgrade conformance tests to Vitest 4 +1/-1

Upgrade conformance tests to Vitest 4

• Updates the conformance package's Vitest development dependency to ^4.1.10.

packages/conformance/package.json

package.jsonUpgrade core tests to Vitest 4 +1/-1

Upgrade core tests to Vitest 4

• Updates the core package's Vitest development dependency to ^4.1.10.

packages/core/package.json

package.jsonUpgrade decorator tests to Vitest 4 +1/-1

Upgrade decorator tests to Vitest 4

• Updates the decorators package's Vitest development dependency to ^4.1.10.

packages/decorators/package.json

package.jsonUpgrade native engine tests to Vitest 4 +1/-1

Upgrade native engine tests to Vitest 4

• Updates the native engine package's Vitest development dependency to ^4.1.10.

packages/engine-native/package.json

package.jsonUpgrade findings tests to Vitest 4 +1/-1

Upgrade findings tests to Vitest 4

• Updates the findings package's Vitest development dependency to ^4.1.10.

packages/findings/package.json

package.jsonUpgrade GitHub integration tests to Vitest 4 +1/-1

Upgrade GitHub integration tests to Vitest 4

• Updates the GitHub integration package's Vitest development dependency to ^4.1.10.

packages/github/package.json

package.jsonUpgrade GitLab integration tests to Vitest 4 +1/-1

Upgrade GitLab integration tests to Vitest 4

• Updates the GitLab integration package's Vitest development dependency to ^4.1.10.

packages/gitlab/package.json

package.jsonUpgrade IR tests to Vitest 4 +1/-1

Upgrade IR tests to Vitest 4

• Updates the intermediate representation package's Vitest development dependency to ^4.1.10.

packages/ir/package.json

package.jsonUpgrade planner tests to Vitest 4 +1/-1

Upgrade planner tests to Vitest 4

• Updates the planner package's Vitest development dependency to ^4.1.10.

packages/planner/package.json

package.jsonUpgrade plugin tests to Vitest 4 +1/-1

Upgrade plugin tests to Vitest 4

• Updates the plugin package's Vitest development dependency to ^4.1.10.

packages/plugin/package.json

package.jsonUpgrade policy tests to Vitest 4 +1/-1

Upgrade policy tests to Vitest 4

• Updates the policy package's Vitest development dependency to ^4.1.10.

packages/policy/package.json

package.jsonUpgrade Docker runtime tests to Vitest 4 +1/-1

Upgrade Docker runtime tests to Vitest 4

• Updates the Docker runtime package's Vitest development dependency to ^4.1.10.

packages/runtime-docker/package.json

package.jsonUpgrade host runtime tests to Vitest 4 +1/-1

Upgrade host runtime tests to Vitest 4

• Updates the host runtime package's Vitest development dependency to ^4.1.10.

packages/runtime-host/package.json

package.jsonUpgrade Podman runtime tests to Vitest 4 +1/-1

Upgrade Podman runtime tests to Vitest 4

• Updates the Podman runtime package's Vitest development dependency to ^4.1.10.

packages/runtime-podman/package.json

package.jsonUpgrade remote runtime tests to Vitest 4 +1/-1

Upgrade remote runtime tests to Vitest 4

• Updates the remote runtime package's Vitest development dependency to ^4.1.10.

packages/runtime-remote/package.json

package.jsonUpgrade runtime tests to Vitest 4 +1/-1

Upgrade runtime tests to Vitest 4

• Updates the base runtime package's Vitest development dependency to ^4.1.10.

packages/runtime/package.json

package.jsonUpgrade SDK tests to Vitest 4 +1/-1

Upgrade SDK tests to Vitest 4

• Updates the SDK package's Vitest development dependency to ^4.1.10.

packages/sdk/package.json

[codacy-production]

Pull Request Overview

The upgrade of the testing framework across the workspace is up to quality standards according to Codacy analysis. However, there is a notable gap between the PR description—which claims alignment of shared test setups—and the actual changes, which only include dependency version bumps. As this is a major version transition affecting 23 packages, there is an inherent risk of breaking changes or deprecated features. The absence of configuration updates suggests that the project may encounter runtime failures if it relies on APIs that have changed in the new version.

About this PR

• The version update affects 23 packages across the monorepo. Comprehensive execution of the full test suite is required to confirm that the environment changes do not introduce regressions or execution failures.
• The transition to a new major version lacks corresponding updates to shared configuration files. It is necessary to verify that the project's test setup and plugins are fully compatible with the new major release's API and defaults.

Test suggestions

• Execute the full test suite across all 23 packages using the updated version to verify no breaking changes were introduced.
• Verify that the workspace-wide test command correctly resolves to the updated version.

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Execute the full test suite across all 23 packages using the updated version to verify no breaking changes were introduced.
2. Verify that the workspace-wide test command correctly resolves to the updated version.

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

Great, no issues found!

Qodo reviewed your code and found no material issues that require review

Tip of the day

💡 Did you know, you can keep summaries lean with Finding overflow, which tucks the rest behind 'View more'

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud