tlamatini-static-version-bumper

To auto-refresh frontend assets, you need cache-busting by bumping the STATIC_VERSION value in your settings.py file. This forces browsers to re-fetch updated CSS and JS bundles instead of loading stale cached versions.

Cache-busting for static files during deployment is best handled by incrementing a STATIC_VERSION variable in your settings file. This updates asset URLs, forcing CDNs and browsers to fetch the latest CSS and JS bundles.

Incrementing a static version variable handles missing STATIC_VERSION values gracefully by signaling no changes were made. It reads the existing version, increments or rotates semver, and returns old_version, new_version, and changed status.

Browsers load old CSS and JS because they cache static assets to improve performance. Without cache-busting, such as updating a STATIC_VERSION in settings.py, browsers continue serving stale bundles instead of re-fetching your updated frontend code.

Cache-busting works for both local development and CDN deployment workflows by updating STATIC_VERSION in settings.py. It ensures browsers and CDNs re-fetch updated CSS and JS bundles whenever frontend changes occur.