Lock file maintenance (main)

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• 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

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm warn Unknown project config "shamefully-hoist". This will stop working in the next major version of npm.
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm warn ERESOLVE overriding peer dependency
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @eslint-community/eslint-utils@4.9.0
npm error Found: dev knip@"^5.33.3" from @eslint-community/eslint-utils@4.9.0
npm error node_modules/.pnpm/@eslint-community+eslint-utils@4.9.0_eslint@9.39.1_jiti@2.6.1_/node_modules/@eslint-community/eslint-utils
npm error   @eslint-community/eslint-utils@4.9.0
npm error   node_modules/.pnpm/eslint-plugin-import-lite@0.3.0_eslint@9.39.1_jiti@2.6.1__typescript@5.9.3/node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.7.0" from eslint-plugin-import-lite@0.3.0
npm error     node_modules/.pnpm/eslint-plugin-import-lite@0.3.0_eslint@9.39.1_jiti@2.6.1__typescript@5.9.3/node_modules/eslint-plugin-import-lite
npm error       eslint-plugin-import-lite@0.3.0
npm error       node_modules/eslint-plugin-import-lite
npm error   @eslint-community/eslint-utils@4.9.0
npm error   node_modules/.pnpm/eslint@9.39.1_jiti@2.6.1/node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.8.0" from eslint@9.39.1
npm error     node_modules/.pnpm/eslint@9.39.1_jiti@2.6.1/node_modules/eslint
npm error       eslint@9.39.1
npm error       node_modules/.pnpm/eslint-plugin-import-lite@0.3.0_eslint@9.39.1_jiti@2.6.1__typescript@5.9.3/node_modules/eslint
npm error       eslint@9.39.1
npm error       node_modules/.pnpm/@eslint-community+eslint-utils@4.9.0_eslint@9.39.1_jiti@2.6.1_/node_modules/eslint
npm error
npm error Could not resolve dependency:
npm error dev knip@"^5.33.3" from @eslint-community/eslint-utils@4.9.0
npm error node_modules/.pnpm/@eslint-community+eslint-utils@4.9.0_eslint@9.39.1_jiti@2.6.1_/node_modules/@eslint-community/eslint-utils
npm error   @eslint-community/eslint-utils@4.9.0
npm error   node_modules/.pnpm/eslint-plugin-import-lite@0.3.0_eslint@9.39.1_jiti@2.6.1__typescript@5.9.3/node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.7.0" from eslint-plugin-import-lite@0.3.0
npm error     node_modules/.pnpm/eslint-plugin-import-lite@0.3.0_eslint@9.39.1_jiti@2.6.1__typescript@5.9.3/node_modules/eslint-plugin-import-lite
npm error       eslint-plugin-import-lite@0.3.0
npm error       node_modules/eslint-plugin-import-lite
npm error   @eslint-community/eslint-utils@4.9.0
npm error   node_modules/.pnpm/eslint@9.39.1_jiti@2.6.1/node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.8.0" from eslint@9.39.1
npm error     node_modules/.pnpm/eslint@9.39.1_jiti@2.6.1/node_modules/eslint
npm error       eslint@9.39.1
npm error       node_modules/.pnpm/eslint-plugin-import-lite@0.3.0_eslint@9.39.1_jiti@2.6.1__typescript@5.9.3/node_modules/eslint
npm error       eslint@9.39.1
npm error       node_modules/.pnpm/@eslint-community+eslint-utils@4.9.0_eslint@9.39.1_jiti@2.6.1_/node_modules/eslint
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-11-10T19_05_09_255Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-11-10T19_05_09_255Z-debug-0.log

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}