chore: bump next from 12.1.4 to 16.2.1 - #309
Conversation
Bumps [next](https://github.com/vercel/next.js) from 12.1.4 to 16.2.1. - [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.1.4...v16.2.1) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
|
Deploy preview for team-scope-test ready! ✅ Preview Built with commit a8ec4f3. |
There was a problem hiding this comment.
1 issue found across 2 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="example/nextjs/package.json">
<violation number="1" location="example/nextjs/package.json:10">
P1: Bumping `next` to 16.2.1 without updating `react` and `react-dom` breaks the peer-dependency contract. Next 16.2.1 requires `react ^18.2.0 || ^19.0.0`, but both are still at `18.0.0`. Bump them to at least `18.2.0` (or to `19.x` if you want the latest).</violation>
</file>
Architecture diagram
sequenceDiagram
participant Browser as Client Browser
participant NextRouter as Next.js Router (App Router)
participant ServerComp as React Server Components
participant ServerAction as NEW: Server Actions
participant DataCache as NEW: Next.js Data Cache
participant ExtAPI as External API / DB
Note over Browser, ExtAPI: Modern Next.js Request Flow (v12 -> v16+)
Browser->>NextRouter: GET /page (RSC Request)
NextRouter->>ServerComp: NEW: Execute Server Component
ServerComp->>DataCache: NEW: fetch() with cache/revalidate
alt Cache Hit
DataCache-->>ServerComp: Return cached data
else Cache Miss / Expired
DataCache->>ExtAPI: Request fresh data
ExtAPI-->>DataCache: Data response
DataCache-->>ServerComp: Return data
end
ServerComp-->>NextRouter: Generate RSC Payload (JSON-like)
NextRouter-->>Browser: NEW: Stream RSC Payload + HTML
Note over Browser, ServerAction: Interaction Flow (Mutations)
Browser->>ServerAction: NEW: POST (Invoke Server Action)
ServerAction->>ExtAPI: Perform Mutation
ExtAPI-->>ServerAction: Success
ServerAction->>DataCache: NEW: revalidatePath() / revalidateTag()
ServerAction-->>NextRouter: Trigger Client-side Refresh
NextRouter->>ServerComp: Re-render affected segments
ServerComp-->>Browser: Update UI (No full page reload)
Note over NextRouter: CHANGED: Middleware and Edge Runtime execution
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| }, | ||
| "dependencies": { | ||
| "next": "12.1.4", | ||
| "next": "16.2.1", |
There was a problem hiding this comment.
P1: Bumping next to 16.2.1 without updating react and react-dom breaks the peer-dependency contract. Next 16.2.1 requires react ^18.2.0 || ^19.0.0, but both are still at 18.0.0. Bump them to at least 18.2.0 (or to 19.x if you want the latest).
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At example/nextjs/package.json, line 10:
<comment>Bumping `next` to 16.2.1 without updating `react` and `react-dom` breaks the peer-dependency contract. Next 16.2.1 requires `react ^18.2.0 || ^19.0.0`, but both are still at `18.0.0`. Bump them to at least `18.2.0` (or to `19.x` if you want the latest).</comment>
<file context>
@@ -7,7 +7,7 @@
},
"dependencies": {
- "next": "12.1.4",
+ "next": "16.2.1",
"react": "18.0.0",
"react-dom": "18.0.0",
</file context>
|
Looks like next is up-to-date now, so this is no longer needed. |



Bumps next from 12.1.4 to 16.2.1.
Release notes
Sourced from next's releases.
... (truncated)
Commits
ed7d2cev16.2.13e37bb4docs: post release amends (#91715)a15ec6edocs: fix broken Activity Patterns demo link in preserving UI state guide (#9...600cd2fFix adapter outputs for dynamic metadata routes (#91680)27886d3Turbopack: fix webpack loader runner layer (#91727)88fc430Fix server actions in standalone mode withcacheComponents(#91711)37aed86turbo-persistence: remove Unmergeable mmap advice (#91713)d6195ecFix layout segment optimization: move app-page imports to server-utility tran...6cb97d6Turbopack: lazy require metadata and handle TLA (#91705)e6b101a[turbopack] Respect{eval:true}in worker_threads constructors (#91666)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 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)