●Change8

Migrating to Next.js v16.3.0-canary.61

Version v16.3.0-canary.61 introduces 1 breaking change. This guide details how to update your code.

Released: 6/23/2026

1
Breaking Changes
2
Migration Steps
3
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

App API routesnext-dev-loop skillnext-cache-components-adoption skill

Breaking Changes

●Issue #1

Removed legacy PPR codepaths, which may break existing configurations relying on them.

Migration Steps

  1. 1
    If relying on legacy PPR codepaths, update configuration as these have been removed.
  2. 2
    Be aware that Cache Components now require a Node.js runtime, as documented.

Release Summary

This release introduces a global opt-in for the runtime stage of Cached Navigations and removes legacy PPR codepaths. It also includes various fixes related to testing, OpenTelemetry attributes, and skill functionality.

Need More Details?

View the full release notes and all changes for Next.js v16.3.0-canary.61.

View Full Changelog