Skip to content

Update dependency eslint to v10#412

Merged
zglicz merged 1 commit intomasterfrom
renovate/major-eslint-monorepo
Feb 9, 2026
Merged

Update dependency eslint to v10#412
zglicz merged 1 commit intomasterfrom
renovate/major-eslint-monorepo

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.210.0.0 age confidence

Release Notes

eslint/eslint (eslint)

v10.0.0

Compare Source


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

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

Rebasing: Never, 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 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 warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/parser@8.54.0
npm error Found: eslint@10.0.0
npm error node_modules/eslint
npm error   dev eslint@"10.0.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.8.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.8.0" from eslint@10.0.0
npm error   1 more (eslint-plugin-notice)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^8.57.0 || ^9.0.0" from @typescript-eslint/parser@8.54.0
npm error node_modules/@typescript-eslint/parser
npm error   dev @typescript-eslint/parser@"8.54.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@9.39.2
npm error node_modules/eslint
npm error   peer eslint@"^8.57.0 || ^9.0.0" from @typescript-eslint/parser@8.54.0
npm error   node_modules/@typescript-eslint/parser
npm error     dev @typescript-eslint/parser@"8.54.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-02-07T08_04_53_839Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-02-07T08_04_53_839Z-debug-0.log

Copy link
Contributor

@zglicz zglicz left a comment

Choose a reason for hiding this comment

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

Auto-approved: Renovate dependency update.

@zglicz zglicz merged commit 127eb8b into master Feb 9, 2026
4 of 6 checks passed
@zglicz zglicz deleted the renovate/major-eslint-monorepo branch February 9, 2026 06:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant