feat(deps): Update eslint monorepo (major) — on hold, reverted to 9.39.4

[renovate]

This PR was intended to apply the following updates:

Package	Change	Age	Confidence
@eslint/js (source)	9.39.4 → 10.0.1
eslint (source)	9.39.4 → 10.5.0

Update: ESLint 10 major bump reverted (on hold)

The ESLint 10 upgrade cannot be completed at this time and has been reverted, keeping eslint and @eslint/js pinned at 9.39.4.

Root cause: eslint-plugin-react@7.37.5 (its latest release) declares a peer of eslint@"^3 || … || ^9.7" and crashes at runtime under ESLint 10 (TypeError: context.getFilename is not a function, an API removed in v10). No published eslint-plugin-react version supports ESLint 10 yet, and it is required by eslint.config.js. This is why Renovate could not regenerate package-lock.json (ERESOLVE), leaving package.json at 10.5.0 while the lock file stayed at 9.39.4 and breaking npm ci in CI.

The other ESLint plugins already support ESLint 10 (eslint-plugin-react-hooks@7.1.1, eslint-plugin-react-refresh@0.5.3), so eslint-plugin-react is the sole blocker.

Changes made: reverted eslint/@eslint/js back to 9.39.4 so package.json and package-lock.json are consistent again. Verified green: npm ci, npm run lint, and all 66 tests pass.

This major bump should remain on hold until eslint-plugin-react ships an ESLint 10-compatible release, at which point Renovate can re-open the update.

---

Release Notes

[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. 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-react@7.37.5
npm error Found: eslint@10.5.0
npm error node_modules/eslint
npm error   dev eslint@"10.5.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.8.0" from eslint@10.5.0
npm error   3 more (eslint-plugin-react-hooks, ...)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7" from eslint-plugin-react@7.37.5
npm error node_modules/eslint-plugin-react
npm error   dev eslint-plugin-react@"7.37.5" from the root project
npm error
npm error Conflicting peer dependency: eslint@9.39.4
npm error node_modules/eslint
npm error   peer eslint@"^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7" from eslint-plugin-react@7.37.5
npm error   node_modules/eslint-plugin-react
npm error     dev eslint-plugin-react@"7.37.5" 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-06-26T21_42_20_005Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-06-26T21_42_20_005Z-debug-0.log

[DevSecNinja]

@copilot Can you investigate the PR comments & CI failures and repair them?

[Copilot]

@copilot Can you investigate the PR comments & CI failures and repair them?

Investigated in 9979065. The CI/Renovate failure is a real, unavoidable dependency conflict, not something fixable in this branch:

• eslint-plugin-react@7.37.5 (its latest release) declares a peer of eslint@"^3 || ... || ^9.7" and crashes at runtime under ESLint 10 (TypeError: context.getFilename is not a function, removed in v10). There is no published eslint-plugin-react version that supports ESLint 10 yet, and it's required by eslint.config.js.
• That's why Renovate couldn't regenerate package-lock.json (ERESOLVE), leaving package.json at 10.5.0 but the lock at 9.39.4 — which breaks npm ci.

The other plugins already support ESLint 10 (eslint-plugin-react-hooks@7.1.1, eslint-plugin-react-refresh@0.5.3), so the sole blocker is eslint-plugin-react.

I reverted eslint/@eslint/js back to 9.39.4 so the branch is consistent and green (npm ci, npm run lint, and all 66 tests pass). This major bump should stay on hold until eslint-plugin-react ships an ESLint 10-compatible release; you may prefer to close this PR and let Renovate re-open it then.