-
Notifications
You must be signed in to change notification settings - Fork 0
[Snyk] Security upgrade eslint from 9.39.4 to 10.0.0 #74
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -51,7 +51,7 @@ | |
| "@modelcontextprotocol/tsconfig": "workspace:^", | ||
| "@modelcontextprotocol/vitest-config": "workspace:^", | ||
| "@typescript/native-preview": "catalog:devTools", | ||
| "eslint": "catalog:devTools", | ||
| "eslint": "10.0.0", | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. WARNING: Incomplete workspace-wide fix — the Reply with There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. WARNING: Potential peer-dependency breakage — the lockfile shows Reply with |
||
| "eslint-config-prettier": "catalog:devTools", | ||
| "eslint-plugin-n": "catalog:devTools", | ||
| "prettier": "catalog:devTools", | ||
|
|
||
There was a problem hiding this comment.
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.yamlstill recordseslint@9.39.4for this package (specifiercatalog: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 itto have Kilo Code address this issue.