ISR revalidate=0 boundary in Next.js 12 reverting static generation to server rendering
Transitioning ISR revalidate configurations between Next.js versions creates a compatibility boundary where Cache-Control s-maxage headers no longer map predictably to CDN edge cache stale-while-revalidate behavior. In Next.js 12, setting revalidate=0 disables static generation and forces server-side rendering, a change altered in subsequent patches, yet the
jamstack