[Snyk] Security upgrade vitest from 4.1.2 to 4.1.8

[snyk-io]

Snyk has created this PR to fix 1 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• packages/server/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue
	Missing Authorization SNYK-JS-VITEST-17375131

Breaking Change Risk

Notice: This assessment is enhanced by AI.

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• Max score is 1000. Note that the real score may have changed since the PR was raised.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

---

Learn how to fix vulnerabilities with free interactive lessons:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

---

This change is 

[snyk-io]

This is a patch upgrade from vitest v4.1.2 to v4.1.8. The releases within this range consist of bug fixes and do not contain any breaking changes.

Key fixes include:

• Preventing test runs from hanging on worker crashes.
• Correcting behavior in browser mode for Playwright routes and session readiness.

No developer action is required for this upgrade.

Source: GitHub Releases

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 661c3ee

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.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

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

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[kilo-code-bot]

WARNING: Hardcoding vitest version bypasses the pnpm catalog abstraction

Pinning "vitest": "4.1.8" directly in one package while all other packages still use catalog:devTools (which resolves to 4.1.2 in the lockfile) creates a version split across the monorepo. The correct approach is to update the devTools catalog specifier in pnpm-workspace.yaml (currently ^4.0.15, which already allows 4.1.8) and regenerate the lockfile via pnpm install --lockfile-only. This keeps all packages on the same version and preserves central catalog management.

---

Reply with @kilocode-bot fix it to have Kilo Code address this issue.

[kilo-code-bot]

Code Review Summary

Status: 1 Issue Found | Recommendation: Address before merge

Overview

Severity	Count
WARNING	1

Issue Details (click to expand)

WARNING

File	Line	Issue
packages/server/package.json	112	Hardcoding vitest version bypasses the pnpm catalog abstraction

Files Reviewed (1 file)

• packages/server/package.json - 1 issue

---

_{Reviewed by step-3.7-flash-20260528 · Input: 199.4K · Output: 8.3K · Cached: 469.9K}

_{Review guidance: REVIEW.md from base branch main}