build(deps-dev): bump eslint-config-next from 16.2.3 to 16.2.4 in /dashboard

[dependabot]

Bumps eslint-config-next from 16.2.3 to 16.2.4.

Release notes

Sourced from eslint-config-next's releases.

v16.2.4

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

Core Changes

• chore: Bump reqwest to 0.13.2 (Fixes Google Fonts with Turbopack for Windows on ARM64) (#92713)
• Turbopack: fix filesystem watcher config not applying follow_symlinks(false) (#92631)
• Scope Safari ?ts= cache-buster to CSS/font assets only (Pages Router) (#92580)
• Compiler: Support boolean and number primtives in next.config defines (#92731)
• turbo-tasks: Fix recomputation loop by allowing cell cleanup on error during recomputation (#92725)
• Turbopack: shorter error for ChunkGroupInfo::get_index_of (#92814)
• Turbopack: shorter error message for ModuleBatchesGraph::get_entry_index (#92828)
• Adding more system info to the 'initialize project' trace (#92427)

Credits

Huge thanks to @​Badbird5907, @​lukesandberg, @​andrewimm, @​sokra, and @​mischnic for helping!

Commits

• 2275bd8 v16.2.4
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[hermes-exosphere]

✅ Auto-approved: all 3 CI checks passing. Ready to merge.

[hermes-exosphere]

Your PR is awaiting review by a moderator. Till then you can join the Discord for conversation: https://discord.gg/qaFM2uYFb

[hermes-exosphere]

Automated code review started - full review. Results will be posted here.

[hermes-exosphere]

🔍 Automated Code Review

📋 Executive Summary

Dependabot bumps eslint-config-next from 16.2.3 to 16.2.4 in /dashboard. This is a patch-level dev dependency update containing Turbopack fixes and compiler improvements. The change is minimal — only version bumps in package.json and package-lock.json. No source code changes required.

---

📊 Change Architecture

graph TD
    A[package.json] -->|"version: 16.2.3 to 16.2.4"| B[eslint-config-next]
    B --> C["@next/eslint-plugin-next 16.2.4"]
    C --> D[ESLint linting rules]
    style B fill:#87CEEB
    style C fill:#87CEEB

Loading

Legend: 🔵 Modified (patch bump only)

---

🔴 Breaking Changes

✅ No breaking changes detected. This is a patch-level bump from 16.2.3 to 16.2.4. The release notes confirm bug fixes only:

• Turbopack filesystem watcher config fix
• reqwest bump for Windows ARM64 Google Fonts
• Compiler boolean/number defines support
• Turbo-tasks recomputation loop fix

---

⚠️ Issues Found

No issues found in this PR.

---

🔬 Logical / Bug Analysis

• Integrity verified: Both eslint-config-next@16.2.4 and @next/eslint-plugin-next@16.2.4 integrity hashes in package-lock.json match the npm registry.
• Dependency tree unchanged: Dependencies (@next/eslint-plugin-next, eslint-import-resolver-node, etc.) remain identical — only the sub-dependency @next/eslint-plugin-next version bumped in lockstep.
• Scope confined: Only 2 files changed, 9 insertions and 9 deletions — purely version strings and integrity hashes.
• No config changes: The eslint config file (eslint.config.mjs) is not touched. No new rules or breaking rule changes between 16.2.3 and 16.2.4.
• Peer dependency warnings: Pre-existing (present in 16.2.3 as well) — eslint 10 + typescript 6 peer dep warnings from the eslint-config-next sub-dependencies. Not introduced or worsened by this bump.

---

🧪 Evidence — Build & Test Results

TypeScript Check

$ npx tsc --noEmit
(exit code 0 — no errors)

Docker Build (npm ci stage)

#9 [deps 3/3] RUN npm ci
#9 209.0 added 458 packages, and audited 459 packages in 3m
#9 209.2 6 vulnerabilities (1 low, 4 moderate, 1 high)

npm ci succeeded with eslint-config-next@16.2.4 installed.

npm Registry Integrity Verification

$ npm view eslint-config-next@16.2.4 dist.integrity
sha512-A6ekXYFj/YQxBPMl45g3e+U8zJo+X2+ZQwcz34pPKjpc/3S4roBA2Rd9xWB4FKuSxhofo1/95WjzmUY+wHrOhg==
✅ Matches lockfile

$ npm view @next/eslint-plugin-next@16.2.4 dist.integrity
sha512-tOX826JJ96gYK/go18sPUgMq9FK1tqxBFfUCEufJb5XIkWFFmpgU7mahJANKGkHs7F41ir3tReJ3Lv5La0RvhA==
✅ Matches lockfile

---

🔗 Issue Linkage

⚠️ No issue linked. This is a routine dependency bump by Dependabot.

---

👥 Human Review Feedback

No human review comments on this PR.

---

💡 Suggestions

None. This is a clean, automated patch bump with no concerns.

---

🏆 Verdict

VERDICT: APPROVED

---

Automated code review · 2026-07-17 12:55 UTC

[hermes-exosphere]

Automated review: Approved. Patch-level dev dependency bump (eslint-config-next 16.2.3 -> 16.2.4). Integrity hashes verified against npm registry. TypeScript check passes. No source code changes, no breaking changes, no config changes. ✅

[hermes-exosphere]

Automated review: Approved. ✅

[hermes-exosphere]

Automated code review started - full review. Results will be posted here.

[hermes-exosphere]

⏳ [progress] Phase 0 complete: reviewed prior discussion and review threads (no unresolved inline threads; no human review feedback). I fetched the exact head commit and am auditing the dependency delta and dashboard validation path.

[hermes-exosphere]

🐳 Starting Docker environment... Repository compose manifests were detected; I am checking whether the root checkout defines a runnable application service before using the dashboard-native validation path.