Next.js 16.3 support — compatibility status and points of attention?

[matbrgz]

Question / Discussion

I'd like to understand the current state of Next.js 16.3 support in
@opennextjs/cloudflare before upgrading a production app.

Current setup

• @opennextjs/cloudflare: ^1.14.7
• next: 15.x
• react / react-dom: 19.2.x
• wrangler: ^4.58.x
• Deploy target: Cloudflare Workers (workerd), Node.js compat

Questions

1. Is Next.js 16.3 supported today? If so, which @opennextjs/cloudflare version is the minimum recommended? Is there a published version compatibility matrix (Next ↔ adapter)?
2. Points of attention when upgrading 15 → 16.3 — any breaking changes the adapter is sensitive to? Specifically:
   • cacheComponents / Partial Prerendering (PPR)
   • the new proxy.js / middleware changes
   • Turbopack as the default build
   • setImmediate / Node built-ins under workerd
   • caching (ISR / revalidateTag) behavior on R2/KV
3. Known open issues to watch for Next 16.x on Cloudflare? (I found [BUG] Next 16 setImmediate crash when uploading OpenNext output directly to WFP via CF API (bypassing wrangler) #1269 setImmediate crash, [BUG] No support for proxy.js in Cloudflare Workers #1277 proxy.js not supported, and [BUG] Prod-only crash when enabling cacheComponents (Uncaught SyntaxError: Unexpected identifier '$') #1130 cacheComponents prod crash — are these the main blockers?)
4. Any recommended upgrade steps or a tracking issue for Next 16 support?

Thanks for the great adapter! 🙏

[DEV-DIBSTER]

As far as I'm aware, Next.js v16.3.0 is still in public preview as of right now. Would be strange to support that version currently.