chore: bump next from 16.2.1 to 16.2.3 - #334
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
dependabot
Bot
added
dependencies
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
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">
P2: Upgrade `eslint-config-next` to the same patch version as `next` so the example does not keep using the older Next ESLint plugin.</violation>
</file>
Architecture diagram
sequenceDiagram
participant Browser as Client Browser
participant NextServer as Next.js Runtime
participant ISRCache as ISR / Data Cache
participant ErrorHooks as onRequestError Hook
Note over Browser, ErrorHooks: Runtime Request & ISR Flow (v16.2.3)
Browser->>NextServer: GET /page
NextServer->>ISRCache: Check entry status (Stale-While-Revalidate)
alt Is Stale (Background Revalidation)
ISRCache-->>NextServer: Return stale data
NextServer-->>Browser: Serve stale page content
NextServer->>NextServer: Trigger background re-render
opt NEW: Revalidation Failure
NextServer->>ErrorHooks: CHANGED: Report ISR error via onRequestError
end
else Is Fresh or First Hit
NextServer->>NextServer: NEW: Concurrency-safe styled-jsx rendering
NextServer-->>Browser: 200 OK (HTML + Assets)
end
Note over Browser, NextServer: Developer Experience (HMR)
opt Dev Mode (HMR)
NextServer->>Browser: NEW: Stable CSS / manifest.ts update
Note right of NextServer: Fixes race conditions in<br/>Safari & manifest HMR
end
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
Comment on lines
+10
to
13
| "next": "16.2.3", | ||
| "react": "19.2.4", | ||
| "react-dom": "19.2.4", | ||
| "vercel": "^41.1.4" |
There was a problem hiding this comment.
P2: Upgrade eslint-config-next to the same patch version as next so the example does not keep using the older Next ESLint plugin.
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>Upgrade `eslint-config-next` to the same patch version as `next` so the example does not keep using the older Next ESLint plugin.</comment>
<file context>
@@ -7,7 +7,7 @@
},
"dependencies": {
- "next": "16.2.1",
+ "next": "16.2.3",
"react": "19.2.4",
"react-dom": "19.2.4",
</file context>
Bumps [next](https://github.com/vercel/next.js) from 16.2.1 to 16.2.3. - [Release notes](https://github.com/vercel/next.js/releases) - [Changelog](https://github.com/vercel/next.js/blob/canary/release.js) - [Commits](vercel/next.js@v16.2.1...v16.2.3) --- updated-dependencies: - dependency-name: next dependency-version: 16.2.3 dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/npm_and_yarn/next-16.2.3
branch
from
April 23, 2026 16:43
3e39cc7 to
fda6fe3
Compare
Contributor
|
Deploy preview for file ready!
Deployed with vercel-action |
Contributor
|
Deploy preview for express-basic-auth ready!
Deployed with vercel-action |
|
Contributor
|
Deploy preview for static ready!
Deployed with vercel-action |
Contributor
Author
|
Superseded by #373. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps next from 16.2.1 to 16.2.3.
Release notes
Sourced from next's releases.
Commits
d5f649bv16.2.32873928[16.x] Avoid consuming cyclic models multiple times (#75)d7c7765[backport]: Ensure app-page reports stale ISR revalidation errors via onReque...c573e8cfix(server-hmr): metadata routes overwrite page runtime HMR handler (#92273)57b8f65next-core: deduplicate output assets and detect content conflicts on emit (#9...f158df1Fix styled-jsx race condition: styles lost due to concurrent rendering (#92459)356d605turbo-tasks-backend: stability fixes for task cancellation and error handling...3b77a6eFix DashMap read-write self-deadlock in task_cache causing hangs (#92210)b2f208aBackport: new view-transitions guide, update and fixes (#92264)52faae3v16.2.2