Skip to content
Open
Changes from all commits
Commits
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 package.json
Original file line number Diff line number Diff line change
Expand Up @@ -69,7 +69,7 @@
"@types/node": "^24.10.1",
"@types/supertest": "catalog:devTools",
"@typescript/native-preview": "catalog:devTools",
"eslint": "catalog:devTools",
"eslint": "10.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

CRITICAL: Lockfile and workspace catalog not updated for eslint@10.0.0

Upgrading root eslint to 10.0.0 while pnpm-lock.yaml still pins eslint: 9.39.4 in the devTools catalog, and while 13 workspace packages still reference catalog:devTools for eslint, creates a split workspace install (root=10.0.0, workspace=9.39.4). The PR description explicitly notes "Failed to update the pnpm-lock.yaml, please update manually before merging." Without updating the catalog/lockfile, pnpm install will either fail or revert to 9.39.4 for workspace consumers, leaving the vulnerability unfixed.


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

"eslint-config-prettier": "catalog:devTools",
"eslint-plugin-n": "catalog:devTools",
"fast-glob": "^3.3.3",
Expand Down
Loading