Skip to content

[Snyk] Security upgrade vitest from 4.1.2 to 4.1.8 #59

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
snyk-io wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Security upgrade vitest from 4.1.2 to 4.1.8 #59

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/client/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -111,7 +111,7 @@
"prettier": "catalog:devTools",
"typescript": "catalog:devTools",
"typescript-eslint": "catalog:devTools",
"vitest": "catalog:devTools",
"vitest": "4.1.8",

@kilo-code-bot kilo-code-bot Bot Jun 29, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

WARNING: Hardcoding vitest 4.1.8 here breaks the monorepo catalog pattern. Every other package (server, core, middleware packages, test packages, examples, root) still uses catalog:devTools for vitest. The correct fix is to update the catalog entry in pnpm-workspace.yaml line 34 from vitest: ^4.0.15 to vitest: ^4.1.8, so all workspace packages stay consistent and the lockfile can be regenerated cleanly. This hardcode creates permanent catalog drift and leaves the Snyk-vulnerable version unresolved in sibling packages.

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

"tsdown": "catalog:devTools"
}
}
Loading