Skip to content

Version app assets to prevent deploy-skew rendering - #22

Merged
MaxGhenis merged 1 commit into
mainfrom
asset-versioning
Aug 10, 2026
Merged

MaxGhenis merged 1 commit into
mainfrom
asset-versioning

Conversation

@MaxGhenis

Copy link
Copy Markdown
Contributor

Fixes the off-by-a-column report from the FY 2025 lens rollout: production markup and row templates are structurally aligned (verified 7-over-7 with 0px header/cell offsets), so the skew was a cached old app.js rendering six cells under the new seven-header table. Assets now share a ?v= stamp — index.html's script tag and app.js's ASSET_V constant, applied to every data fetch — with a lockstep test so bumping one without the other fails CI. Bump the stamp on any deploy that changes an asset.

🤖 Generated with Claude Code

A deploy can leave a browser holding cached app.js against fresh
index.html (or stale data against fresh code), which rendered the
national table visually off by a column during the FY 2025 lens
rollout. Assets now carry a shared cache-buster: index.html loads
app.js?v=<stamp>, app.js declares the same stamp as ASSET_V and
appends it to every data fetch, and a test locks the two in step so a
deploy that bumps one without the other fails CI.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@MaxGhenis
MaxGhenis merged commit 43476e9 into main Aug 10, 2026
1 check passed
@MaxGhenis
MaxGhenis deleted the asset-versioning branch August 10, 2026 01:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant