fix(website): bump styles.css cache-bust to force fresh fetch#88
Merged
Conversation
The opacity fix from PR #87 is live on origin but browsers cached styles.css?v=6 before the deploy. Since the URL didn't change, cached clients keep serving the old CSS. Bumping the version string forces a fresh fetch of the current styles.css for everyone. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Deploying zero-operators with
|
| Latest commit: |
9869da4
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://4e03d2d3.zero-operators.pages.dev |
| Branch Preview URL: | https://claude-website-bust-css-cach.zero-operators.pages.dev |
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
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.
Summary
PR #87 removed the opacity fade on the secondary byline. The CSS file on origin is correct — verified via
curl https://zerooperators.com/styles.css:```
.author-secondary {
display: block;
margin-top: 2px;
}
```
Problem: the HTML loads
styles.css?v=6, the same URL it had before the PR #87 deploy. Browsers that visited the site before PR #87 went live cachedstyles.css?v=6and continue to serve the old CSS (withopacity: 0.55) until the cache expires or the URL changes.This PR bumps the cache-bust string
v=6→v=7so all clients fetch fresh CSS on next page load, picking up the opacity fix immediately.Test plan
<link rel="stylesheet" href="styles.css?v=7">(verified via DOM query)https://zerooperators.com/styles.cssalready has the opacity removed (verified via cache-bustedcurl)zerooperators.comshould now show "WITH CALLUM ADAMSON" at full intensity matching the primary bylineNote on the underlying pattern
Whenever a
.cssfile changes substantively, the?v=query string inwebsite/src/pages/index.html:11should be bumped at the same time. Otherwise, returning visitors will keep seeing the old version. Worth a small mental note for future CSS PRs.🤖 Generated with Claude Code