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 packages/core/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@
"@modelcontextprotocol/tsconfig": "workspace:^",
"@modelcontextprotocol/vitest-config": "workspace:^",
"@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.

WARNING: Lockfile is stale — pnpm-lock.yaml still records eslint@9.39.4 for this package (specifier catalog:devTools). The PR body itself warns: "Failed to update the pnpm-lock.yaml, please update manually before merging." Until the lockfile is updated, this change installs nothing different.


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

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: Incomplete workspace-wide fix — the devTools catalog in pnpm-workspace.yaml still defines eslint: ^9.39.2, and every other package (including the shared @modelcontextprotocol/eslint-config) still uses catalog:devTools. Only packages/core bypasses the catalog, so the vulnerability is not fixed for the rest of the workspace and packages/core now runs eslint@10.0.0 against a shared config resolved for eslint@9.x.


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

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: Potential peer-dependency breakage — the lockfile shows typescript-eslint resolved to 8.57.2(eslint@9.39.4) and eslint-plugin-n to 17.24.0(eslint@9.39.4), indicating these plugins are peer-matched against eslint 9.x. Moving eslint to 10.0.0 without upgrading typescript-eslint and related plugins will likely cause lint failures.


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

"eslint-config-prettier": "catalog:devTools",
"eslint-plugin-n": "catalog:devTools",
"prettier": "catalog:devTools",
Expand Down
Loading