build(deps): bump next from 16.2.10 to 16.2.11

[dependabot]

Bumps next from 16.2.10 to 16.2.11.

Release notes

Sourced from next's releases.

v16.2.11

This release contains security fixes for the following advisories:

High:

• Denial of Service in App Router using Server Actions
• Middleware / Proxy bypass in App Router applications using Turbopack and single locale
• Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
• Server-Side Request Forgery in Server Actions on custom servers

Moderate:

• Cache confusion of response bodies for requests with bodies
• Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
• Denial of Service in the Image Optimization API using SVGs
• Unauthenticated disclosure of internal Server Function endpoints
• Unbounded Server Action payload in Edge runtime

Commits

• 9beca08 v16.2.11
• 3c48c7a [16.x] Fix Turbopack middleware matcher with i18n single locale
• ac1eff3 [16.x] Improve performance of checking valid MPA form submissions
• 9a4651e [16.x] Enforce serverActions.bodySizeLimit for Server Actions in Edge runtime
• b512063 [16.x] Set correct origin for internal redirects in custom server
• d303326 [16.x] Ensure exotic rewrite param values are properly encoded
• 73b9487 [16.x] fix(fetch-cache): key fetch(Request, init) by the effective request
• bf9d17f [16.x] fix(incremental-cache): byte-exact fetch cache key for binary bodies
• fe28768 [16.x] fix(next/image): improve performance of detectContentType()
• d8afb8d [16.x] Performance improvements when decoding React Server function payloads
• 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-apps]

Confidence Score: 4/5

The PR appears safe to merge, although the unrelated lockfile churn should preferably be removed or split into independently reviewable dependency updates.

The five runtime applications consistently receive the intended Next.js security patch, while the only accepted concern is the non-blocking expansion of the lockfile update into unrelated dependency trees.

Files Needing Attention: pnpm-lock.yaml

Important Files Changed

Filename	Overview
apps/auth/package.json	Updates the auth application's exact Next.js dependency to 16.2.11.
apps/chat/package.json	Updates the chat application's exact Next.js dependency to 16.2.11.
apps/frontend-control/package.json	Updates the control application's exact Next.js dependency to 16.2.11.
apps/frontend-manage/package.json	Updates the management application's exact Next.js dependency to 16.2.11.
apps/frontend-pwa/package.json	Updates the student PWA's exact Next.js dependency to 16.2.11.
pnpm-lock.yaml	Resolves Next.js 16.2.11 for the applications but also includes substantial unrelated transitive dependency churn.

_{Reviews (1): Last reviewed commit: "build(deps): bump next from 16.2.10 to 1..." | Re-trigger Greptile}

[greptile-apps]

Unrelated transitive lockfile churn

This lockfile update refreshes unrelated PostCSS, Terser, Azure SDK, MSAL, Babel, and other dependency trees without matching manifest changes, expanding a focused Next.js security patch into dependency upgrades that are harder to review, attribute, and revert independently.

Context Used: CLAUDE.md (source)

Knowledge Base Used: Monorepo Tooling and CI

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.