Skip to content

CHANGELOG.md

Latest commit

 

History

History
15 lines (8 loc) · 1.16 KB

CHANGELOG.md

File metadata and controls

15 lines (8 loc) · 1.16 KB
Raw

Changelog

0.9.0

Changed

  • revalidateTag no longer deletes the underlying cache entries it revalidates. This matches Next.js's own built-in FileSystemCache.revalidateTag, which never deletes entries either — staleness is tracked via the shared tagsManifest instead, so the last-good value stays servable while Next revalidates in the background (and so cacheComponents/PPR routes can resume from the cached postponed state).

    If you relied on the previous behavior (cache entries being physically deleted on revalidateTag), this is a behavior change: entries now remain readable until overwritten by a subsequent set.

  • revalidateTag now accepts an optional second durations argument ({ expire?: number }), matching Next's CacheHandler.revalidateTag signature. Passing { expire: N } sets a future expiry (soft/background revalidation) instead of the immediate hard expiry used when no durations are provided.

Fixed

  • Fixed a race condition in the build-prerender fallback lazy-init (getBuildPrerender) where concurrent first-miss callers could read a not-yet-assigned instance field as a false miss. Now memoized as an in-flight promise.