Changelog: Async stale-while-revalidate (Cache)#28577
Changelog: Async stale-while-revalidate (Cache)#28577pedrosousa merged 7 commits intocloudflare:productionfrom
Conversation
|
/bonk review this changelog using the changelog skill and make suggestions (only) for any improvements required |
There was a problem hiding this comment.
Good changelog entry overall — clear explanation of the change and its impact. A few items to address:
- Anchor link likely broken — The link
/cache/concepts/cache-control/#stale-while-revalidatepoints to a heading that does not exist. The relevant heading incache-control.mdxis### Revalidation(anchor#revalidation). - Existing docs now contradict this changelog —
src/content/docs/cache/concepts/cache-control.mdxat line 82 still says: "Currently,stale-while-revalidateblocks on the first request..." along with lines 83-87 explaining the old synchronous behavior. These should be updated in a separate or accompanying PR to reflect the new async behavior, or readers will see conflicting information. - Minor style nits inline below.
src/content/changelog/cache/2026-02-24-async-stale-while-revalidate.mdx
Outdated
Show resolved
Hide resolved
src/content/changelog/cache/2026-02-24-async-stale-while-revalidate.mdx
Outdated
Show resolved
Hide resolved
src/content/changelog/cache/2026-02-24-async-stale-while-revalidate.mdx
Outdated
Show resolved
Hide resolved
|
Review submitted. Here's a summary of the feedback: Findings:
|
…idate.mdx Co-authored-by: ask-bonk[bot] <249159057+ask-bonk[bot]@users.noreply.github.com>
…idate.mdx Co-authored-by: ask-bonk[bot] <249159057+ask-bonk[bot]@users.noreply.github.com>
…idate.mdx Co-authored-by: ask-bonk[bot] <249159057+ask-bonk[bot]@users.noreply.github.com>
|
/bonk review the added changes for completeness |
…r async SWR - REVALIDATED: reframe as the synchronous validation path, now only seen without stale-while-revalidate or when must-revalidate/no-cache (with OCC enabled) prevents stale serving - UPDATING: remove misleading 'very popular resources' qualifier; explain it as the expected status during async stale-while-revalidate revalidation - cache-control example: remove 'initial synchronous revalidation' language - retention-vs-freshness: update revalidation paragraph to distinguish async (SWR) and synchronous paths Companion to cloudflare#28577
pedrosousa noted on cloudflare#28577 that synchronous revalidation is still the live behaviour for Enterprise zones not yet migrated, so past tense is factually incorrect for those users. Also scope the situations where REVALIDATED is seen to explicitly include unmigraded Enterprise zones.
Summary
New changelog entry for async stale-while-revalidate (Cache)
Documentation checklist