Update eslint monorepo to v9.29.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@eslint/js (source)	9.25.1 -> 9.29.0
eslint (source)	9.25.1 -> 9.29.0

---

Release Notes

eslint/eslint (@​eslint/js)

v9.29.0

Compare Source

v9.28.0

Compare Source

v9.27.0

Compare Source

v9.26.0

Compare Source

eslint/eslint (eslint)

v9.29.0

Compare Source

v9.28.0

Compare Source

v9.27.0

Compare Source

v9.26.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: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

---

This change is 

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[BoomchainLabs]

GitKraken automatically performed 2 actions

• assigned @BoomchainLabs
  Action
  https://gitkraken.dev/automations/8435c8eb-9b0e-435e-b54b-c2f06fac390a
• added reviewer @BoomchainLabs
  Action
  https://gitkraken.dev/automations/8435c8eb-9b0e-435e-b54b-c2f06fac390a

Create your own automations at gitkraken.dev/automations

[netlify]

❌ Deploy Preview for chonk9k failed. Why did it fail? →

Name	Link
🔨 Latest commit	7c24b8f
🔍 Latest deploy log	https://app.netlify.com/projects/chonk9k/deploys/68439c7c4ce40d00080a1234

[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 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: recharts@2.13.3
npm error Found: react@19.1.0
npm error node_modules/react
npm error   peer react@">=16.8.0" from @floating-ui/react-dom@2.1.3
npm error   node_modules/@floating-ui/react-dom
npm error     @floating-ui/react-dom@"^2.0.0" from @radix-ui/react-popper@1.2.7
npm error     node_modules/@radix-ui/react-popper
npm error       @radix-ui/react-popper@"1.2.7" from @radix-ui/react-hover-card@1.1.14
npm error       node_modules/@radix-ui/react-hover-card
npm error         @radix-ui/react-hover-card@"^1.1.2" from the root project
npm error       4 more (@radix-ui/react-menu, @radix-ui/react-popover, ...)
npm error   peer react@"^16.8 || ^17.0 || ^18.0 || ^19.0 || ^19.0.0-rc" from @radix-ui/react-accordion@1.2.11
npm error   node_modules/@radix-ui/react-accordion
npm error     @radix-ui/react-accordion@"^1.2.1" from the root project
npm error   77 more (@radix-ui/react-alert-dialog, @radix-ui/react-arrow, ...)
npm error
npm error Could not resolve dependency:
npm error peer react@"^16.0.0 || ^17.0.0 || ^18.0.0" from recharts@2.13.3
npm error node_modules/recharts
npm error   recharts@"^2.13.0" from the root project
npm error
npm error Conflicting peer dependency: react@18.3.1
npm error node_modules/react
npm error   peer react@"^16.0.0 || ^17.0.0 || ^18.0.0" from recharts@2.13.3
npm error   node_modules/recharts
npm error     recharts@"^2.13.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/2025-06-13T18_39_19_378Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-06-13T18_39_19_378Z-debug-0.log