Fix blocking revalidation for `fetch` and `unstable_cache`
The incremental cache now reads the Resume Data Cache (RDC) during on-demand revalidation before it bypasses persisted entries. Both `unstable_cache` and cached `fetch` calls use this path, so the final prerender does not repeat asynchronous work and fail with `NEXT_STATIC_GEN_BAILOUT`. This extends the fix proposed in PR #100895 to cached fetches and preserves the forced-refresh behavior introduced in PR #48516. The incremental cache continues to apply its tag invalidation checks before it returns an entry. Fixes #99866 Closes #100895
Showing
Please
register
or
sign in
to comment