Update dependency @10up/eslint-config to v3.1.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@10up/eslint-config (source)	3.0.0 -> 3.1.1

---

Release Notes

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

v3.1.1

Compare Source

Patch Changes

• a930021: Fix: prettier peerDependency range

v3.1.0

Compare Source

Minor Changes

• f3122e4: Updating several dependencies
  Better error messages when svg parsing fails

Patch Changes

• Updated dependencies [f3122e4]
  • @​10up/babel-preset-default@​2.1.0

---

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: 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]

⚠ 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

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @10up/[email protected]
npm ERR! Found: @wordpress/[email protected]
npm ERR! node_modules/@wordpress/eslint-plugin
npm ERR!   dev @wordpress/eslint-plugin@"^14.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @wordpress/eslint-plugin@"^13.10.0" from @10up/[email protected]
npm ERR! node_modules/@10up/eslint-config
npm ERR!   @10up/eslint-config@"3.1.1" from the root project
npm ERR!   peer @10up/eslint-config@"^3.0.0" from [email protected]
npm ERR!   node_modules/10up-toolkit
npm ERR!     dev 10up-toolkit@"^5.1.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @wordpress/[email protected]
npm ERR! node_modules/@wordpress/eslint-plugin
npm ERR!   peerOptional @wordpress/eslint-plugin@"^13.10.0" from @10up/[email protected]
npm ERR!   node_modules/@10up/eslint-config
npm ERR!     @10up/eslint-config@"3.1.1" from the root project
npm ERR!     peer @10up/eslint-config@"^3.0.0" from [email protected]
npm ERR!     node_modules/10up-toolkit
npm ERR!       dev 10up-toolkit@"^5.1.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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/38b497/1906b1/cache/others/npm/_logs/2023-07-19T14_03_25_132Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/38b497/1906b1/cache/others/npm/_logs/2023-07-19T14_03_25_132Z-debug-0.log

[renovate]

⚠️ 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: @10up/[email protected]
npm ERR! Found: @wordpress/[email protected]
npm ERR! node_modules/@wordpress/eslint-plugin
npm ERR!   dev @wordpress/eslint-plugin@"^14.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peerOptional @wordpress/eslint-plugin@"^13.10.0" from @10up/[email protected]
npm ERR! node_modules/@10up/eslint-config
npm ERR!   @10up/eslint-config@"3.1.1" from the root project
npm ERR!   peer @10up/eslint-config@"^3.0.0" from [email protected]
npm ERR!   node_modules/10up-toolkit
npm ERR!     dev 10up-toolkit@"^5.1.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @wordpress/[email protected]
npm ERR! node_modules/@wordpress/eslint-plugin
npm ERR!   peerOptional @wordpress/eslint-plugin@"^13.10.0" from @10up/[email protected]
npm ERR!   node_modules/@10up/eslint-config
npm ERR!     @10up/eslint-config@"3.1.1" from the root project
npm ERR!     peer @10up/eslint-config@"^3.0.0" from [email protected]
npm ERR!     node_modules/10up-toolkit
npm ERR!       dev 10up-toolkit@"^5.1.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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-12-09T00_25_21_485Z-debug-0.log