Long-Term Caching - CI/CD Glossary Definition
Long-term caching serves hashed assets with a far-future expiry so returning users skip the download entirely.
Long-term caching is serving static assets with a far-future cache lifetime so browsers reuse them across visits. It is safe only when filenames include a content hash that changes on every content change.
Pairing content-hashed filenames with a long max-age (often marked immutable) lets browsers cache assets for a year while still fetching updates when content changes. In CI, the production build produces the hashed filenames this strategy depends on.
Related guides
Content Hash - CI/CD Glossary DefinitionContent Hash: A content hash is a hash computed from a file contents, used in output filenames so the name ch…
Cache Busting - CI/CD Glossary DefinitionCache Busting: Cache busting forces clients to download a new version of a file by changing its URL, usually…
Asset Hashing - CI/CD Glossary DefinitionAsset Hashing: Asset hashing embeds a content-derived hash in output filenames (for example `app.3f9a1c.js`)…