Conversation
Bumps [next](https://github.com/vercel/next.js) from 14.2.32 to 16.0.5. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v14.2.32...v16.0.5) --- updated-dependencies: - dependency-name: next dependency-version: 16.0.5 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Comment |
| "@vercel/og": "^0.8.5", | ||
| "classnames": "^2.5.1", | ||
| "next": "^14.2.32", | ||
| "next": "^16.0.5", |
There was a problem hiding this comment.
Bug: Next.js 16 upgrade without required React 19
This PR upgrades next from version 14 to 16 but keeps react and react-dom at version ^18.3.1. Next.js 15+ was designed for and documented with React 19, and the official upgrade guide recommends upgrading both together (npm i next@latest react@latest react-dom@latest). Running Next.js 16 with React 18 is not an officially supported configuration and could cause runtime issues, missing features, or hydration mismatches.
|
Superseded by #1601. |
Bumps next from 14.2.32 to 16.0.5.
Release notes
Sourced from next's releases.
... (truncated)
Commits
89ccb9fv16.0.575f63f7backport fix(nodejs-middleware): await for body cloning to be properly finali...d440c75v16.0.4296923eTurbopack: fix passing project options from napi (#86256)98317f5fix: prevent fetch abort errors propagating to user error boundaries (#86277)7780025fix: Rename proxy.js to middleware.js in NFT file (#86214)2eda33cv16.0.300cb5d9perf: revert to use the light safe stringify for is-error (#86053)de6bc15docs: keywords in system reqs and add browserslist (#85838)a51b804docs: cacheHandlers (#85311)Most Recent Ignore Conditions Applied to This Pull Request
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Note
Upgrade Next.js from 14.2.32 to 16.0.5 with corresponding SWC/runtime updates and new optional sharp image pipeline deps.
nextfrom^14.2.32to^16.0.5inpackage.json.@next/env,@next/swc-*binaries,@swc/helpers(0.5.15), andstyled-jsx(5.1.6).sharp@^0.34.4and related platform packages (@img/*), plus supporting deps (detect-libc@^2,semver@^7.7.3,@emnapi/runtime).busboy,streamsearch).Written by Cursor Bugbot for commit 2e2ed6e. This will update automatically on new commits. Configure here.