Asset Hashing - CI/CD Glossary Definition
Asset hashing puts a content hash in each filename so browsers cache aggressively yet still fetch updates.
Asset hashing embeds a content-derived hash in output filenames (for example app.3f9a1c.js) so the URL changes only when the content changes. This enables safe long-term caching and cache busting.
When a file changes, its hash changes, producing a new URL that bypasses stale caches; unchanged files keep their URL and stay cached. The build writes a manifest mapping logical names to hashed files. In CI, asset hashing is part of the production build.
Related guides
Cache Busting - CI/CD Glossary DefinitionCache Busting: Cache busting forces clients to download a new version of a file by changing its URL, usually…
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…
Long-Term Caching - CI/CD Glossary DefinitionLong-Term Caching: Long-term caching is serving static assets with a far-future cache lifetime so browsers re…