1. 23 May, 2024 3 commits
    • vercel-release-bot's avatar
      v14.3.0-canary.78 · 6cacc83d
      vercel-release-bot authored
      6cacc83d
    • JJ Kasper's avatar
      [Breaking] Disable automatic fetch caching (#66004) · 4d14e831
      JJ Kasper authored
      ## Background
      
      Previously we introduced automatic caching for `fetch` based on certain
      heuristics that were a bit tricky to grasp all scenarios. The scenarios
      we would automatically cache were no dynamic data access before the
      fetch call e.g. `headers()` or `cookies()`, the fetch call is inside of
      a dynamic page e.g. `POST` method or `export const revalidate = 0` page
      and the fetch is a non-`GET` request or has `Authorization` or `Cookie`
      headers, or the fetch had `cache: 'no-store' | 'no-cache'` or
      `revalidate: 0`.
      
      ## New Behavior
      
      By default fetches will no longer automatically be cached. Instead they
      need to be opted-in to caching via `export const fetchCache =
      'default-cache' | 'force-cache',` `next: { revalidate: false or value >
      0 }` or `cache: 'force-cache' | 'default-cache'`.
      
      When the fetch call is automatically skipping the cache it won't impact
      the page level ISR cacheability although if a fetch call manually
      specifies `cache: 'no-store'` or `revalidate: 0` it will still bail from
      the page being statically generated as it was before.
      
      To achieve the previous behavior of automatic fetch caching all that
      needs to be added is `export const fetchCache = 'default-cache'` in the
      root layout(s) of your project.
      4d14e831
    • Wyatt Johnson's avatar
      fix: ensure prefetch data routes are always added when app has ppr enabled (#66102) · 6c1c0049
      Wyatt Johnson authored
      When PPR is enabled, we should always write the prefetch RSC routes to
      ensure that the builder and FS cache can use it.
      6c1c0049
  2. 22 May, 2024 15 commits
  3. 21 May, 2024 22 commits