chore(deps): bump next from 12.3.4 to 14.2.35 #401
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.
|
PR SummaryUpgrades Next.js from 12 to 14 and refreshes the lockfile with associated dependency updates (SWC, styled-jsx, PostCSS, binaries).
Written by Cursor Bugbot for commit f906c04. Configure here. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Bug: Next.js 14 requires React 18 but React 17 remains
Next.js 14 declares a peer dependency on react: ^18.2.0 and react-dom: ^18.2.0, but the project continues to use react: ^17.0.2 and react-dom: ^17.0.2. This peer dependency mismatch means Next.js 14 features that depend on React 18 APIs (like Server Components, concurrent rendering, and streaming) may fail at runtime or behave unexpectedly. Upgrading to Next.js 14 requires also upgrading React to version 18.
package.json#L49-L56
Lines 49 to 56 in f906c04
pnpm-lock.yaml#L3296-L3298
Lines 3296 to 3298 in f906c04
Comment @cursor review or bugbot run to trigger another review on this PR
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.