next.js

The recent Cached Navigations feature introduced navigation-level caching into the segment cache, where static and dynamic RSC data from navigations and initial HTML loads is cached so that repeat visits can be served instantly. This feature is currently gated behind , meaning it activates for all projects that enable Cache Components. This change introduces a new flag that independently controls the Cached Navigations behavior. The flag defaults to so we can investigate potential regressions that the feature might have introduced without affecting the broader Cache Components functionality. The flag requires to also be enabled and throws a configuration error if is set without it. On the server, the staged rendering paths in (both RSC request handling and initial HTML rendering) now check before producing staged responses. On the client, is used alongside for compile-time dead code elimination in the stream tee () and the response processing (). The cached navigations test suite enables the flag via , and the Cache Components CI jobs export to maintain test coverage.