deps: update nextjs monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@next/eslint-plugin-next (source)	15.5.12 → 15.5.15
eslint-config-next (source)	15.5.12 → 15.5.15
next (source)	16.2.3 → 16.2.4

---

Release Notes

vercel/next.js (@​next/eslint-plugin-next)

v15.5.15

Compare Source

Please refer the following changelogs for more information about this security release:

https://vercel.com/changelog/summary-of-cve-2026-23869

v15.5.14

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• feat(next/image): add lru disk cache and images.maximumDiskCacheSize (#​91660)
• Fix(pages-router): restore Content-Length and ETag for /_next/data/ JSON responses (#​90304)

Credits

Huge thanks to @​styfle and @​lllomh for helping!

v15.5.13

Compare Source

[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.

Core Changes

• fix: patch http-proxy to prevent request smuggling in rewrites (See: CVE-2026-29057)

Credits

Huge thanks to @​ztanner for helping!

vercel/next.js (eslint-config-next)

v15.5.15

Compare Source

v15.5.14

Compare Source

v15.5.13

Compare Source

vercel/next.js (next)

v16.2.4

Compare Source

---

Configuration

📅 Schedule: (in timezone Europe/Tallinn)

• Branch creation
  • "after 9am and before 7pm every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: eslint-config-custom@1.0.0
npm error Found: eslint@10.2.0
npm error node_modules/eslint
npm error   dev eslint@"10.2.0" from eslint-config-custom@1.0.0
npm error   packages/eslint-config-custom
npm error     eslint-config-custom@1.0.0
npm error     node_modules/eslint-config-custom
npm error       workspace packages/eslint-config-custom from the root project
npm error       1 more (clearance_ui)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.23.0 || ^8.0.0 || ^9.0.0" from eslint-config-next@15.5.15
npm error node_modules/eslint-config-next
npm error   dev eslint-config-next@"15.5.15" from eslint-config-custom@1.0.0
npm error   packages/eslint-config-custom
npm error     eslint-config-custom@1.0.0
npm error     node_modules/eslint-config-custom
npm error       workspace packages/eslint-config-custom from the root project
npm error       1 more (clearance_ui)
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-04-22T23_37_26_214Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-04-22T23_37_26_214Z-debug-0.log