Bump next from 15.5.9 to 16.1.7 in /agentex-ui

[dependabot]

Bumps next from 15.5.9 to 16.1.7.

Release notes

Sourced from next's releases.

v16.1.7

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

Core Changes

• [Cache Components] Prevent streaming fetch calls from hanging in dev (#89194)
• Apply server actions transform to node_modules in route handlers (#89380)
• ensure maxPostponedStateSize is always respected (See: CVE-2026-27979)
• feat(next/image): add lru disk cache and images.maximumDiskCacheSize (See: CVE-2026-27980)
• Allow blocking cross-site dev-only websocket connections from privacy-sensitive origins (See: CVE-2026-27977)
• Disallow Server Action submissions from privacy-sensitive contexts by default (See: CVE-2026-27978)
• fix: patch http-proxy to prevent request smuggling in rewrites (See: CVE-2026-29057)

Credits

Huge thanks to @​unstubbable, @​styfle, @​eps1lon, and @​ztanner for helping!

v16.1.6

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

Core Changes

• Upgrade to swc 54 (#88207)
• implement LRU cache with invocation ID scoping for minimal mode response cache (#88509)
• tweak LRU sentinel key (#89123)

Credits

Huge thanks to @​mischnic, @​wyattjoh, and @​ztanner for helping!

v16.1.5

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

https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472 https://vercel.com/changelog/summary-of-cve-2026-23864

v16.0.11

Please see this changelog for more information about this security patch.

v15.6.0-canary.61

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

• https://vercel.com/changelog/summaries-of-cve-2025-59471-and-cve-2025-59472
• https://vercel.com/changelog/summary-of-cve-2026-23864

v15.5.13

[!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)

... (truncated)

Commits

• bdf3e35 v16.1.7
• dc98c04 [backport]: fix: patch http-proxy to prevent request smuggling in rewrites (#...
• 9023c0a [backport] Disallow Server Action submissions from privacy-sensitive contexts...
• 36a97b9 Allow blocking cross-site dev-only websocket connections from privacy-sensiti...
• 93c3993 [backport]: feat(next/image): add lru disk cache and `images.maximumDiskCache...
• c68d62d Backport documentation fixes for 16.1.x (#90655)
• 5214ac1 [backport]: ensure maxPostponedStateSize is always respected (#90060) (#90471)
• c95e357 Backport/docs fixes 16.1.x (#90125)
• cba6144 [backport] Apply server actions transform to node_modules in route handlers...
• 3db9063 [backport] [Cache Components] Prevent streaming fetch calls from hanging in d...
• Additional commits viewable 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Greptile Summary

This PR is a dependabot-generated security upgrade bumping next from 15.5.9 to 16.1.7, patching five CVEs (including request smuggling, Server Action abuse, cross-site WebSocket connections, and image cache issues). The package-lock.json is updated accordingly with new resolutions for transitive dependencies like sharp and @emnapi/runtime.

• Security fixes included: CVE-2026-27977, CVE-2026-27978, CVE-2026-27979, CVE-2026-27980, CVE-2026-29057 — all addressed in the new version.
• Major version bump: This is a 15.x → 16.x jump; while dependabot indicates a compatibility score, any breaking changes in Next.js 16 for the app's routing, image optimization, or server actions should be validated against the running application.
• eslint-config-next version mismatch: eslint-config-next remains at 15.4.5 while next is now 16.1.7. These two packages are tightly coupled and should be kept in sync to avoid linting issues.

Confidence Score: 3/5

• This PR is mostly safe to merge given the important security fixes, but the eslint-config-next version mismatch and the major version jump warrant validation before merging.
• The bump addresses multiple CVEs which makes merging desirable, but the eslint-config-next / next version mismatch (15.4.5 vs 16.1.7) could break the lint pipeline. Additionally, a major version bump (15→16) should be smoke-tested against the running app to catch any breaking API changes.
• agentex-ui/package.json — eslint-config-next needs to be updated to match next@16.1.7

Important Files Changed

Filename	Overview
agentex-ui/package.json	Bumps next from 15.5.9 to 16.1.7 (major version bump), but eslint-config-next in devDependencies remains at 15.4.5, creating a version mismatch.
agentex-ui/package-lock.json	Lock file updated by dependabot to reflect the new next@16.1.7 resolution along with updated transitive dependencies (sharp, @emnapi/runtime, etc.).

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[dependabot bumps next\n15.5.9 → 16.1.7] --> B[package.json updated]
    B --> C[next: 16.1.7 ✅]
    B --> D[eslint-config-next: 15.4.5 ⚠️ not updated]
    C --> E[Security CVEs patched\nCVE-2026-27977\nCVE-2026-27978\nCVE-2026-27979\nCVE-2026-27980\nCVE-2026-29057]
    D --> F[Version mismatch may cause\nnext lint failures or\nincorrect ESLint rule behavior]

Loading

Comments Outside Diff (1)

1. agentex-ui/package.json, line 69 (link)

   eslint-config-next version mismatch with next

   next has been bumped to 16.1.7 (a major version change), but eslint-config-next in devDependencies is still pinned at 15.4.5. The eslint-config-next package is tightly coupled to the Next.js version — using a mismatched version can cause lint failures, incorrect rule behavior, or errors when running next lint.

   This should be updated to match the installed Next.js version:

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: agentex-ui/package.json
   Line: 69
   
   Comment:
   **`eslint-config-next` version mismatch with `next`**
   
   `next` has been bumped to `16.1.7` (a major version change), but `eslint-config-next` in `devDependencies` is still pinned at `15.4.5`. The `eslint-config-next` package is tightly coupled to the Next.js version — using a mismatched version can cause lint failures, incorrect rule behavior, or errors when running `next lint`.
   
   This should be updated to match the installed Next.js version:
   
   
   
   How can I resolve this? If you propose a fix, please make it concise.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: agentex-ui/package.json
Line: 69

Comment:
**`eslint-config-next` version mismatch with `next`**

`next` has been bumped to `16.1.7` (a major version change), but `eslint-config-next` in `devDependencies` is still pinned at `15.4.5`. The `eslint-config-next` package is tightly coupled to the Next.js version — using a mismatched version can cause lint failures, incorrect rule behavior, or errors when running `next lint`.

This should be updated to match the installed Next.js version:

```suggestion
    "eslint-config-next": "16.1.7",
```

How can I resolve this? If you propose a fix, please make it concise.

_{Last reviewed commit: "Bump next from 15.5...."}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​next@​15.5.9 ⏵ 16.1.7		+20

View full report