high85%
Next 16.3 regression: htmlLimitedBots matching browser UAs forces cacheable PPR pages to private/no-store
In Next.js 16.3, when cacheComponents is enabled and htmlLimitedBots is configured as a broad regex (e.g. /.*/), ordinary browser user agents matching the pattern are treated as limited bots, causing shouldForceDynamicPPRRender to become true. This disables SSG/cacheable PPR responses and emits private, no-cache, no-store, max-age=0, must-revalidate for all such requests, even though the route metadata is compatible with streaming. In 16.2.11 the same configuration kept browser requests cacheable. This regresses CDN cache hit rates and increases origin load.