Skip to content

Update dependency @10up/eslint-config to v5 - #72

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/10up-eslint-config-5.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/10up-eslint-config-5.x

Conversation

@renovate

@renovate renovate Bot commented Sep 28, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@10up/eslint-config (source) ^4.0.0 → ^5.0.0 age confidence

Release Notes

10up/10up-toolkit (@​10up/eslint-config)

v5.0.0

Compare Source

Major Changes
  • e40dc56: Support and default to Node 24

    Node 24 (current Active LTS) is now the version the toolkit is developed, tested and released against, and the minimum supported Node version is now 20. Node 16 and 18 are past end-of-life and have been dropped from the test matrix; CI now covers Node 20, 22 and 24.

    This is a breaking change only in the sense that engines no longer permits Node 16/18. No build, config or API behaviour has changed — see UPGRADING.md for details.

Patch Changes

v4.1.4

Compare Source

Patch Changes
  • 064daa3: Bump eslint-config-prettier and eslint-plugin-prettier

v4.1.3

Compare Source

Patch Changes
  • be6517d: restrict eslint-plugin-jest to <v29

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 commented Sep 28, 2026 •

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: Amphiblocks@1.0.0
npm ERR! Found: @10up/eslint-config@3.0.0
npm ERR! node_modules/@10up/eslint-config
npm ERR!   @10up/eslint-config@"^5.0.0" from the root project
npm ERR!   peer @10up/eslint-config@"^3.0.0" from 10up-toolkit@5.1.0
npm ERR!   node_modules/10up-toolkit
npm ERR!     dev 10up-toolkit@"^6.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! @10up/eslint-config@"^5.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: prettier@3.9.9
npm ERR! node_modules/prettier
npm ERR!   peer prettier@">=3.0.0" from @10up/eslint-config@5.0.0
npm ERR!   node_modules/@10up/eslint-config
npm ERR!     @10up/eslint-config@"^5.0.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-10-01T04_06_56_375Z-debug-0.log

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.

0 participants