- Shipped
- August 19, 2026 at 7:59 PM UTC
- Author
- Kamo
- Commit
- c51fc2c
The playlists were the last entry in Lighthouse's cache-lifetime audit — 300s originally, then an hour, still reported. Everything else in the ladder was already immutable; the playlists were the exception, and at 1 KiB they were the whole remaining item. They are immutable for a year now, both here and on the live objects, which were set directly since this job no-ops while the source hash matches and would not otherwise have rewritten them. This moves a cost rather than removing one, so the comment says so plainly: a re-encode will not reach a browser that has already cached them. The mitigation is the `?v=` on HERO_HLS_SRC in the marketing site's Hero.tsx — that query string is the cache key for the master playlist, and the master is what names the variant playlists, so one bump invalidates the whole ladder. Both files carry the instruction, because the failure mode otherwise is a re-encode that looks like this job silently did nothing.