Skip to content
Open
Show file tree
Hide file tree
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 apps/agentprofiles-cli/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@
"zod": "^4.3.6"
},
"devDependencies": {
"@eslint/js": "^9.39.2",
"@eslint/js": "^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.

@eslint/js@^10 declares Node engine support ^20.19.0 || ^22.13.0 || >=24 and a (optional) peer on eslint@^10, but this package still advertises engines.node: >=18 and pins eslint@^9.39.2, so installs/linting may break under Node 18 / ESLint 9 (also applies to the other updated package.json files).

Severity: medium

Other Locations
  • apps/clones-cli/package.json:58
  • apps/vsix-bridge-cli/package.json:54

Generating Fix in Augment link...

🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Lock files not updated for two apps

High Severity

The package.json files for agentprofiles-cli and vsix-bridge-cli were updated to @eslint/js: ^10.0.0, but their respective package-lock.json files were not updated — they still declare @eslint/js: ^9.39.2 and resolve to version 9.39.4. Only the clones-cli lockfile was updated. This lockfile/package.json mismatch will cause npm ci to fail in those two apps.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 6554009. Configure here.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

eslint v9 incompatible with @eslint/js v10 peer

Medium Severity

@eslint/js is bumped to ^10.0.0 but eslint remains at ^9.39.2. The @eslint/js@10 package declares a peer dependency on eslint: ^10.0.0 and includes breaking changes such as an updated eslint:recommended configuration and removed deprecated APIs. Using @eslint/js@10 configs with eslint@9 can cause runtime failures if the recommended config references rules or options unavailable in v9.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 6554009. Configure here.

"@tsconfig/node18": "^18.2.4",
"@tsconfig/strictest": "^2.0.8",
"@types/node": "^25.3.0",
Expand Down
18 changes: 13 additions & 5 deletions apps/clones-cli/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion apps/clones-cli/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@
"update-notifier": "^7.3.1"
},
"devDependencies": {
"@eslint/js": "^9.39.2",
"@eslint/js": "^10.0.0",
"@types/node": "^25.3.0",
"@types/update-notifier": "^6.0.8",
"eslint-config-prettier": "^10.1.8",
Expand Down
2 changes: 1 addition & 1 deletion apps/vsix-bridge-cli/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@
"update-notifier": "^7.3.1"
},
"devDependencies": {
"@eslint/js": "^9.39.2",
"@eslint/js": "^10.0.0",
"@tsconfig/node18": "^18.2.4",
"@tsconfig/strictest": "^2.0.8",
"@types/node": "^25.3.0",
Expand Down
Loading