Chore(deps-dev): Bump next from 12.3.1 to 16.0.5 in /website

[dependabot]

Bumps next from 12.3.1 to 16.0.5.

Release notes

Sourced from next's releases.

v16.0.5

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

Core Changes

• fix(nodejs-middleware): await for body cloning to be properly finalized (#85418)

Credits

Huge thanks to @​lucasadrianof for helping!

v16.0.4

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

Core Changes

• fix: Rename proxy.js to middleware.js in NFT file (#86214)
• fix: prevent fetch abort errors propagating to user error boundaries (#86277)
• Turbopack: fix passing project options from napi (#86256)

Credits

Huge thanks to @​devjiwonchoi, @​sokra and @​ztanner for helping!

v16.0.3

Core Changes

• fix: Rspack throw error when using ForceCompleteRuntimePlugin: #85221
• fix: build CLI output not displaying Proxy (Middleware) when nodejs runtime: #85403
• fix: staleTimes.static should consistently enforce a 30s minimum: #85479
• [turbopack] fix build of empty entries of pages: #84873
• Cache the head separately from the route tree: #84724
• Allow inspecting dev server on default port with next dev --inspect: #85037
• Avoid proxying React modules through workUnitStore: #85486
• fix: redirect should always return updated router state: #85533
• Upgrade React from b4455a6e-20251027 to 4f931700-20251029: #85518
• [turbopack] Move generation of cacheLife types out of the webpack plugin and into the dev bundler directly: #85539
• Ensure user-space stack frame for 'use cache' in page/layout component: #85519
• Update parallel routes in build-complete: #85546
• fully remove clientSegmentCache flag: #85541
• [turbopack] Support relative paths in turbopack source maps.: #85146
• Release unnecessary memory on hydration finish: #84967
• Preserve interception markers in parameter types: #85526
• move segment cache entries to top level segment-cache dir: #85542
• Upgrade React from 4f931700-20251029 to 561ee24d-20251101: #85670
• [devtools] Remove title from preferences: #85698
• Update font data: #85708
• Don't invalidate hot reloader excessively during dev server boot: #85732

... (truncated)

Commits

• 89ccb9f v16.0.5
• 75f63f7 backport fix(nodejs-middleware): await for body cloning to be properly finali...
• d440c75 v16.0.4
• 296923e Turbopack: fix passing project options from napi (#86256)
• 98317f5 fix: prevent fetch abort errors propagating to user error boundaries (#86277)
• 7780025 fix: Rename proxy.js to middleware.js in NFT file (#86214)
• 2eda33c v16.0.3
• 00cb5d9 perf: revert to use the light safe stringify for is-error (#86053)
• de6bc15 docs: keywords in system reqs and add browserslist (#85838)
• a51b804 docs: cacheHandlers (#85311)
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Labels

The following labels could not be found: pr/no-changelog, type/docs-cherrypick. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[sentry]

Bug: Next.js 16 requires Node.js 20.9+, but .nvmrc specifies Node.js 14, causing incompatibility.
_{Severity: CRITICAL | Confidence: High}

🔍 Detailed Analysis

The project's .nvmrc file specifies Node.js v14, which is incompatible with Next.js 16.0.5. Next.js 16 requires Node.js 20.9 or later. Attempting to build or run the project with Node.js v14 will result in immediate failure, as Next.js 16 cannot operate on this older version. The package.json engines field also lacks a node version constraint, preventing automatic warnings.

💡 Suggested Fix

Update .nvmrc to specify Node.js v20.9 or later. Consider adding a node version constraint to the engines field in package.json for explicit enforcement.

🤖 Prompt for AI Agent

Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: website/package.json#L8

Potential issue: The project's `.nvmrc` file specifies Node.js `v14`, which is
incompatible with Next.js `16.0.5`. Next.js 16 requires Node.js `20.9` or later.
Attempting to build or run the project with Node.js `v14` will result in immediate
failure, as Next.js 16 cannot operate on this older version. The `package.json`
`engines` field also lacks a `node` version constraint, preventing automatic warnings.

_{Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 3920074}

[dependabot]

Superseded by #795.