The direction was from "cached unless you opt out" to "uncached unless you opt in".
Next.js 14. The docs promised to "cache as much as possible". A fetch with no cache option used force-cache unless the route used a dynamic function or config, so data could stay in the data cache indefinitely. GET route handlers were prerendered at build unless they read the request. The client router cache kept dynamic pages for 30 seconds and static ones for 5 minutes.
Next.js 15 made all three uncached by default. A fetch with no options became no-store-like; the 16.4.5 docs call it auto no cache: run once at build if the route is static, on every request if it is dynamic. GET handlers render per request. staleTimes.dynamic went from 30 to 0, so <Link> refetches dynamic pages, though shared layouts, loading.js and back/forward still reuse the cache. The release post's reason: feedback on the opinionated defaults, and how they would interact with Partial Prerendering and third-party libraries using fetch. A library's internal fetch could be cached without its author or user knowing.
Next.js 16 didn't flip anything back. It added cacheComponents, an opt-in model where nothing is cached unless marked use cache, and changed caching APIs: revalidateTag now takes a cacheLife profile as its second argument, with updateTag for immediate expiry from Server Actions (per the upgrade guide, not run here). With Cache Components off, 16.4.5 behaves like 15.
Opting back in is per layer: cache: 'force-cache' or next.revalidate on a fetch, fetchCache = 'default-cache' on a segment, dynamic = 'force-static' on a handler, experimental.staleTimes for the router cache.
The 14 behaviour above is from the 14 docs and the 15 release posts, not run here; the 15 defaults were observed on 16.4.5.