chore(deps): bump next from 16.1.1 to 16.1.7 in /apps/web

[dependabot]

Bumps next from 16.1.1 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

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 bump of next from 16.1.1 to 16.1.7 in apps/web/package.json, addressing multiple high-severity CVEs (including request smuggling via http-proxy, Server Action abuse from privacy-sensitive contexts, and cross-site dev WebSocket exposure).

Key issue found:

• The root-level bun.lock file was not updated alongside package.json. All next-related entries in the lockfile (next, @next/env, and all @next/swc-* platform binaries) still reference 16.1.1. Because Bun uses the lockfile as the source of truth for installed versions, the security patches introduced in 16.1.5–16.1.7 will not be applied until bun install is run and the updated bun.lock is committed.

Important Files Changed

Filename	Overview
apps/web/package.json	Bumps next from 16.1.1 to 16.1.7 to address multiple security CVEs, but the root bun.lock was not updated, so the actual installed version at build/deploy time remains 16.1.1 until the lockfile is regenerated.

Prompt To Fix All With AI

This is a comment left during a code review.
Path: apps/web/package.json
Line: 47

Comment:
**Lockfile not updated — security patches not yet effective**

The `package.json` has been bumped to `next@16.1.7`, but the root-level `bun.lock` still pins the old version. Specifically, `bun.lock` contains:

- Line 79: `"next": "16.1.1"` (workspace manifest entry)
- Line 1974: `"next": ["next@16.1.1", ...]`
- All `@next/swc-*` optional dependencies still at `16.1.1`

Because Bun installs the exact resolution locked in `bun.lock` rather than re-resolving from `package.json`, the five CVEs addressed in 16.1.5–16.1.7 (including `CVE-2026-27978`, `CVE-2026-29057`, and others) will **not** be patched in practice until the lockfile is regenerated.

To fix, run `bun install` after this `package.json` change and commit the updated `bun.lock`.

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

_{Last reviewed commit: 5b19d9f}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Lockfile not updated — security patches not yet effective

The package.json has been bumped to next@16.1.7, but the root-level bun.lock still pins the old version. Specifically, bun.lock contains:

• Line 79: "next": "16.1.1" (workspace manifest entry)
• Line 1974: "next": ["next@16.1.1", ...]
• All @next/swc-* optional dependencies still at 16.1.1

Because Bun installs the exact resolution locked in bun.lock rather than re-resolving from package.json, the five CVEs addressed in 16.1.5–16.1.7 (including CVE-2026-27978, CVE-2026-29057, and others) will not be patched in practice until the lockfile is regenerated.

To fix, run bun install after this package.json change and commit the updated bun.lock.

Prompt To Fix With AI

This is a comment left during a code review.
Path: apps/web/package.json
Line: 47

Comment:
**Lockfile not updated — security patches not yet effective**

The `package.json` has been bumped to `next@16.1.7`, but the root-level `bun.lock` still pins the old version. Specifically, `bun.lock` contains:

- Line 79: `"next": "16.1.1"` (workspace manifest entry)
- Line 1974: `"next": ["next@16.1.1", ...]`
- All `@next/swc-*` optional dependencies still at `16.1.1`

Because Bun installs the exact resolution locked in `bun.lock` rather than re-resolving from `package.json`, the five CVEs addressed in 16.1.5–16.1.7 (including `CVE-2026-27978`, `CVE-2026-29057`, and others) will **not** be patched in practice until the lockfile is regenerated.

To fix, run `bun install` after this `package.json` change and commit the updated `bun.lock`.

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