Bump next and next-auth in /apps/functional_chat

[dependabot]

Bumps next and next-auth. These dependencies needed to be updated together.
Updates next from 14.2.35 to 16.2.12

Release notes

Sourced from next's releases.

v16.2.12

What's Changed

• Backport/docs fixes 16.2 - July round by @​icyJoseph in vercel/next.js#96031
• [Backport] Fixes to support TypeScript 7 by @​lukesandberg in vercel/next.js#95831

Full Changelog: vercel/next.js@v16.2.11...v16.2.12

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

v16.2.10

Contains no changes except publishing @next/swc-wasm-web which was accidentally not published since 16.2.4.

v16.2.9

Empty release to ensure next@latest points at a stable release. Next.js only allows publishing with Trusted Publishing enabled. In order to fix NPM dist-tags, we have to release a new version. Updating dist-tags is not possible with Trusted Publishing.

v16.2.8

Release with no changes in an attempt to fix next@latest pointing at a prerelease version.

v16.2.7

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

Core Changes

• Backport documentation fixes for v16.2 (#93804)
• [backport] Patch playwright-core to resolve _finishedPromise on requestFailed (#93920)
• [backport] Fix dev mode hydration failure when page is served from HTTP cache (#93492)
• [backport] Fix catch-all router.query corruption with basePath + rewrites (#93917)
• [backport] Encode non-ASCII characters in cache tags at construction (#93918)
• [backport] Fix server action forwarding loop with middleware rewrites (#93919)
• [backport] Turbopack: switch from base40 to base38 hash encoding (#93932)
• [ci] Disable hanging node 24 typescript tests on 16.2 backport branch (#94164)

... (truncated)

Commits

• 2234717 v16.2.12
• 957f5ed [Backport] Fixes to support TypeScript 7 (#95831)
• b56eb16 Backport/docs fixes 16.2 - July round (#96031)
• 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
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for next since your current version.

Updates next-auth from 4.24.5 to 4.24.15

Release notes

Sourced from next-auth's releases.

next-auth@4.24.15

Security patch release for the 4.x line.

• getToken() now returns null instead of throwing when the Authorization header contains a malformed Bearer value.
• OAuth state, nonce, and PKCE check cookies are now bound to the provider that created them and are rejected when a different provider handles the callback. Sign-ins in flight across the upgrade fail once and succeed on retry.
• Email addresses are Unicode-normalized (NFKC) before validation in the email sign-in flow, closing a homoglyph @ bypass.
• An explicitly configured NEXTAUTH_URL now takes precedence over the auto-detected forwarded host in trusted-host mode.
• Restores CommonJS compatibility by pinning uuid to ^11.1.1; the 14.x line is ESM-only and broke require() on Node versions below 20.19.

next-auth@4.24.14

Bugfixes

• providers: add issuer to GitHub provider for RFC 9207 compliance (#13412)

GitHub now returns an iss parameter in OAuth callbacks. openid-client validates it unconditionally, which was breaking authentication for apps that didn't configure an issuer. This sets the default GitHub provider issuer to https://github.com/login/oauth.

Commits

• d857eec chore(release): next-auth@4.24.15 [skip ci]
• 5bca239 fix(next-auth): harden getToken parsing and bind OAuth check cookies to provi...
• db7e27d chore(deps): use uuid ^11.1.1 to keep CommonJS support (#13466)
• 32d874c fix(next-auth): repair red v4 CI (lint + pre-existing test drift) (#13447)
• fa85858 chore: update uuid to v14, remove deprecated types (#13422)
• 2a39465 Merge commit from fork
• 19d2feb Merge commit from fork
• e9a892a chore(release): bump version [skip ci]
• 0497da4 fix(providers): add issuer to github (#13412)
• 1a70ee8 chore(release): bump version [skip ci]
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by better-gustavo, a new releaser for next-auth since your current version.

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.

---

Note

High Risk
A two-major-version Next jump affects routing, middleware, and build/runtime behavior; next-auth 4.24.15 includes OAuth/cookie security changes that can break in-flight sign-ins once.

Overview
Upgrades Next.js in functional_chat from 14.2.35 to 16.2.12 (two major versions) and refreshes the lockfile so next-auth resolves to 4.24.15. There are no application source changes—only package.json and package-lock.json.

The lockfile shift reflects Next 16’s stack: Node >=20.9.0 (up from 18.17), optional sharp for image optimization, updated @next/swc-* binaries, and styled-jsx 5.1.6. Transitive auth-related bumps include cookie 0.7.x and uuid 11.x under next-auth.

Review note: package.json still declares engines.node": ">=18.15.0", which is below Next 16’s requirement—CI and deploy images should run Node 20.9+. eslint-config-next / @next/eslint-plugin-next remain on older 13.x lines while Next is 16; worth validating lint and next build after merge.

^{Reviewed by Cursor Bugbot for commit 9340928. Bugbot is set up for automated code reviews on this repo. Configure here.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
functional-chat	Error		Jul 30, 2026 3:36pm
transcription-demo	Ready	Preview	Jul 30, 2026 3:36pm

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 9340928. Configure here.}

[cursor]

Node version below Next 16 floor

High Severity

Bumping next to 16.2.12 requires Node >=20.9.0, but engines still allows >=18.15.0 and .nvm pins v18.17.0. Installs and runs on the project’s current Node 18 setup will fail against Next’s new engine floor.

Additional Locations (2)

• apps/functional_chat/package-lock.json#L9006-L9008
• apps/functional_chat/package.json#L7-L10

 

^{Reviewed by Cursor Bugbot for commit 9340928. Configure here.}

[cursor]

Webpack config breaks Turbopack default

High Severity

Next 16 defaults to Turbopack and errors when a webpack config is present without a Turbopack migration or --webpack opt-out. This app still defines a custom webpack hook and wraps config with @vanilla-extract/next-plugin@2.1.1, so next dev / next build are likely to fail after the bump.

 

^{Reviewed by Cursor Bugbot for commit 9340928. Configure here.}

[cursor]

Risk: high. Left a non-blocking comment — not approving: Cursor Bugbot ended in skip with 2 unresolved high-severity findings, and this Next 14→16 plus next-auth bump exceeds the low-risk auto-approve threshold (auth/runtime blast radius). Assigning reviewers for human review of the major upgrade and the failed functional-chat deploy.

  

_{Sent by Cursor Approval Agent: Pull Request Approver}