Skip to content

chore: update dependency eslint to v10#55

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-eslint
Open

chore: update dependency eslint to v10#55
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-eslint

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Feb 7, 2026

This PR contains the following updates:

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

Release Notes

eslint/eslint (eslint)

v10.0.0

Compare Source

v9.39.2

Compare Source


Configuration

📅 Schedule: Branch creation - "after 10pm,before 5:00am" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Feb 7, 2026
@renovate
Copy link
Contributor Author

renovate bot commented Feb 7, 2026

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: eslint-plugin-bpmn-io@2.2.0
npm ERR! Found: eslint@10.0.0
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^10.0.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.9.0
npm ERR!   node_modules/@eslint-community/eslint-utils
npm ERR!     @eslint-community/eslint-utils@"^4.8.0" from eslint@10.0.0
npm ERR!   2 more (eslint-plugin-mocha, eslint-utils)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^9" from eslint-plugin-bpmn-io@2.2.0
npm ERR! node_modules/eslint-plugin-bpmn-io
npm ERR!   dev eslint-plugin-bpmn-io@"^2.2.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: eslint@9.39.2
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^9" from eslint-plugin-bpmn-io@2.2.0
npm ERR!   node_modules/eslint-plugin-bpmn-io
npm ERR!     dev eslint-plugin-bpmn-io@"^2.2.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-07T01_51_40_143Z-debug-0.log

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

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants