Skip to content

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

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 #60

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/server/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -109,6 +109,6 @@
"tsdown": "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 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.

}
}
Loading