Artifact release map / Reading notes
Cache HTML and assets deliberately
Two classes of files need different update behaviour.
Version immutable files
Use content-derived or release-specific names for assets. Long-lived caching is appropriate only when a URL will not later serve different bytes.
Keep the entry point fresh
Choose an HTML revalidation policy that matches the release process. A stale document may keep referencing assets from an older version.
Retain referenced assets
Do not remove previous files immediately after publication. Open tabs and cached HTML may still request them during the transition.