Skip to content

Update npm package eslint to v10#120

Open
renovate[bot] wants to merge 1 commit intomainfrom
deps/js/major-eslint-npm-packages
Open

Update npm package eslint to v10#120
renovate[bot] wants to merge 1 commit intomainfrom
deps/js/major-eslint-npm-packages

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented Feb 14, 2026

This PR contains the following updates:

Package Change Age Confidence
eslint (source) ^9.39.2^10.0.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

eslint/eslint (eslint)

v10.0.2

Compare Source

v10.0.1

Compare Source

Bug Fixes

Documentation

  • 5b3dbce docs: add AI acknowledgement section to templates (#​20431) (루밀LuMir)
  • 6f23076 docs: toggle nav in no-JS mode (#​20476) (Tanuj Kanti)
  • b69cfb3 docs: Update README (GitHub Actions Bot)

Chores

v10.0.0

Compare Source

v9.39.3

Compare Source

Bug Fixes

  • 791bf8d fix: restore TypeScript 4.0 compatibility in types (#​20504) (sethamus)

Chores


Configuration

📅 Schedule: Branch creation - "before 4am every weekday,every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@cursor
Copy link
Copy Markdown

cursor bot commented Feb 14, 2026

PR Summary

Medium Risk
Tooling-only change, but ESLint v10 and its transitive deps raise Node engine requirements (to Node 20+/22+), which could break installs/linting in environments still on Node 18.

Overview
Upgrades eslint from ^9.39.2 to ^10.0.0 for both agentprofiles-cli and vsix-bridge-cli.

Regenerates the two package-lock.json files to reflect ESLint v10’s updated dependency tree (notably newer @eslint/* packages and minimatch), including removals/reshuffles of some previously bundled transitive deps.

Written by Cursor Bugbot for commit c134017. This will update automatically on new commits. Configure here.

@vercel
Copy link
Copy Markdown

vercel bot commented Feb 14, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
petrinaut-hazel Ready Ready Preview, Comment Feb 27, 2026 11:06am

@augmentcode
Copy link
Copy Markdown

augmentcode bot commented Feb 14, 2026

🤖 Augment PR Summary

Summary: Updates the vsix-bridge CLI’s development tooling to use ESLint v10.
Change: Bumps the eslint devDependency in apps/vsix-bridge-cli from ^9.39.2 to ^10.0.0 to keep linting dependencies current.

🤖 Was this summary useful? React with 👍 or 👎

Copy link
Copy Markdown

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

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

Review completed. 2 suggestions posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

"@types/semver": "^7.7.1",
"@types/update-notifier": "^6.0.8",
"eslint": "^9.39.2",
"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.

This repo uses package-lock.json, but it currently still pins eslint to ^9.39.2; without regenerating the lockfile, npm ci will likely not pick up ESLint v10.

Severity: medium

Fix This in Augment

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

"@types/semver": "^7.7.1",
"@types/update-notifier": "^6.0.8",
"eslint": "^9.39.2",
"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.

typescript-eslint (used in eslint.config.js) currently has peer deps that only allow ESLint ^8.57.0 || ^9.0.0 per the existing lockfile, so moving to ESLint v10 may trigger an ERESOLVE/peer-dep conflict during install.

Severity: high

Fix This in Augment

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

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

"@types/node": "^25.3.0",
"@types/update-notifier": "^6.0.8",
"eslint": "^9.39.2",
"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.

Node engine range now mismatches eslint

Medium Severity

Upgrading to eslint@^10.0.0 introduces a Node requirement of ^20.19.0 || ^22.13.0 || >=24, but both packages still declare engines.node as >=18. This creates an inconsistent contract where npm run lint can fail on supported Node 18 environments.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant