Skip to content

chore(deps): update dependency eslint to v10.3.0#5625

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

chore(deps): update dependency eslint to v10.3.0#5625
renovate[bot] wants to merge 1 commit intomainfrom
renovate/eslint-monorepo

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 4, 2026

This PR contains the following updates:

Package Change Age Confidence
eslint (source) 10.2.110.3.0 age confidence

Release Notes

eslint/eslint (eslint)

v10.3.0

Compare Source


  • 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 May 4, 2026
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented May 4, 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: frontend/package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-plugin-import@2.32.0
npm error Found: eslint@10.3.0
npm error node_modules/eslint
npm error   dev eslint@"10.3.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.9.1
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.9.1" from @typescript-eslint/utils@8.59.1
npm error     node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"^8.58.0" from @vitest/eslint-plugin@1.6.16
npm error       node_modules/@vitest/eslint-plugin
npm error         dev @vitest/eslint-plugin@"1.6.16" from the root project
npm error       2 more (eslint-plugin-storybook, eslint-plugin-testing-library)
npm error     @eslint-community/eslint-utils@"^4.8.0" from eslint@10.3.0
npm error   12 more (@eslint/compat, @eslint/js, @typescript-eslint/utils, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9" from eslint-plugin-import@2.32.0
npm error node_modules/eslint-plugin-import
npm error   dev eslint-plugin-import@"2.32.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@9.39.4
npm error node_modules/eslint
npm error   peer eslint@"^2 || ^3 || ^4 || ^5 || ^6 || ^7.2.0 || ^8 || ^9" from eslint-plugin-import@2.32.0
npm error   node_modules/eslint-plugin-import
npm error     dev eslint-plugin-import@"2.32.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps 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-05-06T05_37_26_378Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-06T05_37_26_378Z-debug-0.log

@renovate renovate Bot force-pushed the renovate/eslint-monorepo branch from fe573ae to 72bc447 Compare May 5, 2026 03:24
@renovate renovate Bot force-pushed the renovate/eslint-monorepo branch from 72bc447 to a22fed8 Compare May 6, 2026 05:37
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