Fix: Cache busting for production frontend assets#1471
Merged
Conversation
Set no-cache on index.html so users always get the latest version. Set immutable 1-year cache on content-hashed JS/CSS files.
deep1401
approved these changes
Mar 6, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Users sometimes get cached (stale) versions of the app after a new build because JS/CSS filenames don't change between deploys, and
index.htmlhas no cache-control headers.Solution
1. Content-hashed filenames (webpack)
[name].js→[name].[contenthash:8].jsstyle.css→style.[contenthash:8].cssHtmlWebpackPluginautomatically injects the new hashed filenames intoindex.html2. Cache-control headers (FastAPI)
no-cache, no-store, must-revalidateonindex.htmlso browsers always re-fetch itCache-Control: public, max-age=31536000, immutablefor aggressive long-term cachingUnchanged vendor chunks keep their hash and stay cached, so only modified bundles are re-downloaded.