Skip to content

Bump patch supported range to 16.0.8 #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
k0d13 merged 1 commit into from
Dec 11, 2025
Merged

Bump patch supported range to 16.0.8 #152

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/v1cAoMtrJsWo7.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"next-ws": patch
---

Bump patch supported range to 16.0.8
90 changes: 45 additions & 45 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion pnpm-workspace.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@ packages:
- "examples/*"

catalog:
next: "16.0.7"
next: "16.0.8"
Copy link

@coderabbitai coderabbitai bot Dec 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Next.js 16.0.8 release npm registry

💡 Result:

Yes — Next.js 16.0.8 is published. Install with:

npm install [email protected]

Sources showing the 16.0.8 release/artifact: [NewReleases (next releases list)] [1], [Fossies archive (next.js‑16.0.8 tarball) ] [2].

References:

  1. NewReleases — next release list (includes 16.0.8). [1]
  2. Fossies — next.js-16.0.8 tar.gz (Dec 8, 2025). [2]

🌐 Web query:

Next.js 16.0.8 breaking changes known issues

💡 Result:

Key breaking changes in Next.js 16 (and known issues reported):

  • Async-only Request APIs: synchronous access to cookies(), headers(), draftMode(), params, and searchParams is removed — you must await them. (nextjs.org)
  • Minimum platform bumps: Node.js minimum is 20.9+, TypeScript minimum 5.1; older runtimes will fail. (medium.com)
  • Cache Components / caching model changes: new "use cache"/Cache Components model and changes to unstable_cache/serialization behavior may surface runtime serialization errors with some libraries (reports exist). (infoq.com)
  • Turbopack is default (webpack opt‑out): build/dev behavior changed — some custom webpack setups or plugins may break or require adjustments. (infoq.com)
  • Middleware and routing changes: middleware.ts → proxy.ts and other router/edge API adjustments require config/code updates. (medium.com)
  • Removed features: AMP support removed; some deprecated CLI/commands (e.g., internal next lint flow) have changed. (medium.com)

Notable known issues and advisories:

  • Serialization/timing bug with unstable_cache causing "Objects are not valid as a React child" in some setups; workaround: deep-clone (JSON) before rendering. (GitHub issue). (github.com)
  • Security advisories affecting recent Next.js versions (including 16.x) — check Next.js/Vercel security notices and upgrade patches immediately. (nextjs.org)

If you want, I can fetch the official Next.js 16 migration guide and the specific GitHub issues relevant to your app (e.g., Turbopack, unstable_cache) and summarize recommended code changes.

Citations:

Verify workspace compatibility with Next.js 16.0.8 breaking changes.

Next.js 16.0.8 exists and is published, but introduces significant breaking changes requiring careful migration:

  • Async-only APIs: cookies(), headers(), draftMode(), params, and searchParams must now be awaited
  • Runtime requirements: Node.js 20.9+ and TypeScript 5.1+ minimum
  • Turbopack default: Webpack is now opt-out; custom webpack setups may break
  • Middleware changes: middleware.ts → proxy.ts pattern
  • Cache model changes: New "use cache" and Cache Components; known serialization issues with unstable_cache ("Objects are not valid as a React child")
  • Removed features: AMP support removed

Confirm that existing patch definitions, application code, and build configuration are compatible with these breaking changes before merging.

🤖 Prompt for AI Agents 
In pnpm-workspace.yaml around line 6 (the Next.js version entry), the upgrade to
next: "16.0.8" may introduce multiple breaking changes; before merging, update
the workspace and CI config to require Node >=20.9 and TypeScript >=5.1 (update
package.json "engines" and CI images), run codebase-wide search for usages of
cookies(), headers(), draftMode(), params, and searchParams and update call
sites to await them and adjust any server/client boundary logic, verify custom
webpack setups and opt out/in Turbopack by explicitly setting next.config.js
experimental/turbopack flags or retain webpack config, rename/adjust any
middleware.ts to proxy.ts patterns and related imports, audit caching usage
replacing unstable_cache with new cache APIs and add tests to catch
serialization issues, and validate any patch definitions or postinstall scripts
that assume removed features (AMP) or old APIs; run full test/build in a Node
20.9+ environment and fix reported runtime/type errors before merging.

react: "19.1.1"
react-dom: "19.1.1"
"@types/react": "19.1.10"
2 changes: 1 addition & 1 deletion src/patches/patch-2.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,7 +21,7 @@ export const patchCookies = definePatchStep({

export default definePatch({
name: 'patch-2',
versions: '>=15.0.0 <=16.0.7',
versions: '>=15.0.0 <=16.0.8',
steps: [
p1_patchNextNodeServer,
p1_patchRouterServer,
Expand Down