Bump next from 12.3.4 to 14.2.35 #1751
Conversation
Bumps [next](https://github.com/vercel/next.js) from 12.3.4 to 14.2.35. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v12.3.4...v14.2.35) --- updated-dependencies: - dependency-name: next dependency-version: 14.2.35 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![sentry[bot]](https://avatars.githubusercontent.com/u/1396951?s=60&v=4){kind=small}
| "jszip": "^3.10.1", | ||
| "jszip-utils": "^0.1.0", | ||
| "lodash": "^4.17.21", | ||
| "luxon": "^3.5.0", |
There was a problem hiding this comment.
Bug: The upgrade to Next.js 14 requires React 18, but the package.json still specifies React 17. This will cause a runtime crash on application start.
Severity: CRITICAL | Confidence: High
🔍 Detailed Analysis
Upgrading Next.js to version 14 introduces a dependency on React 18.2.0 or higher. The current package.json updates next to ^14.2.35 but leaves react and react-dom at ^17.0.2. Next.js 14 relies on the createRoot API, which is only available in React 18. Since React 17 does not provide this API, the application will throw a runtime error and crash when it attempts to render any page.
💡 Suggested Fix
Update the react and react-dom dependencies in package.json to a version compatible with Next.js 14, such as ^18.2.0.
🤖 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: package.json#L58
Potential issue: Upgrading Next.js to version 14 introduces a dependency on React 18.2.0
or higher. The current `package.json` updates `next` to `^14.2.35` but leaves `react`
and `react-dom` at `^17.0.2`. Next.js 14 relies on the `createRoot` API, which is only
available in React 18. Since React 17 does not provide this API, the application will
throw a runtime error and crash when it attempts to render any page.
Did we get this right? 👍 / 👎 to inform future reviews.
Reference ID: 7457324
Bumps next from 12.3.4 to 14.2.35.
Release notes
Sourced from next's releases.
Commits
7b940d9v14.2.357c1be85Backport facebook/react#35351 for 14.2.34 (#87095)f307368v14.2.348e43882Update React Version (#36)385e8c2Backport Next.js changes to v14.2.34 (#29)7a2cf51update version script778e7bflock swc binaries5a97b40v14.2.33cb88824backport(v14): omit searchParam data from FlightRouterState before transport ...89ee561v14.2.32Dependabot 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)You can disable automated security fix PRs for this repo from the Security Alerts page.