Skip to content

chore(deps): update eslint monorepo to v8.57.1#248

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

chore(deps): update eslint monorepo to v8.57.1#248
renovate[bot] wants to merge 1 commit into
developfrom
renovate/eslint-monorepo

Conversation

@renovate

@renovate renovate Bot commented Dec 10, 2024

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
eslint (source) 8.57.08.57.1 age confidence

Release Notes

eslint/eslint (eslint)

v8.57.1

Compare Source


Configuration

📅 Schedule: (UTC)

  • 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: 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 force-pushed the renovate/eslint-monorepo branch from c0e54e6 to d0d0281 Compare August 10, 2025 12:32
@renovate

renovate Bot commented Nov 11, 2025

Copy link
Copy Markdown
Contributor Author

⚠️ 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: @newlevelup/remark-config@1.0.9
npm ERR! Found: remark@15.0.1
npm ERR! node_modules/remark
npm ERR!   dev remark@"15.0.1" from the root project
npm ERR!   remark@"^15.0.0" from remark-cli@12.0.1
npm ERR!   node_modules/remark-cli
npm ERR!     dev remark-cli@"12.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer remark@"14.0.3" from @newlevelup/remark-config@1.0.9
npm ERR! node_modules/@newlevelup/remark-config
npm ERR!   dev @newlevelup/remark-config@"1.0.9" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: remark@14.0.3
npm ERR! node_modules/remark
npm ERR!   peer remark@"14.0.3" from @newlevelup/remark-config@1.0.9
npm ERR!   node_modules/@newlevelup/remark-config
npm ERR!     dev @newlevelup/remark-config@"1.0.9" 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! 
npm ERR! For a full report see:
npm ERR! /runner/cache/others/npm/_logs/2026-06-01T19_09_34_548Z-eresolve-report.txt

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

@renovate renovate Bot force-pushed the renovate/eslint-monorepo branch from d0d0281 to e5a1fc1 Compare November 11, 2025 01:32
@renovate renovate Bot force-pushed the renovate/eslint-monorepo branch from e5a1fc1 to 8500011 Compare March 5, 2026 14:34
@renovate renovate Bot force-pushed the renovate/eslint-monorepo branch 2 times, most recently from 1055d8c to afc8a7d Compare April 1, 2026 19:58
@renovate renovate Bot force-pushed the renovate/eslint-monorepo branch from afc8a7d to d321bb3 Compare May 12, 2026 09:15
@renovate renovate Bot changed the title chore(deps): update dependency eslint to v8.57.1 chore(deps): update eslint monorepo to v8.57.1 Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants