Force CSS fingerprint regeneration to bust CloudFront cache #16275
Conversation
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
This comment was marked as resolved.
This comment was marked as resolved.
Collaborator
|
Your site preview for commit 7982a40 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16275-7982a40c.s3-website.us-west-2.amazonaws.com. |
The current build process fingerprints CSS before PurgeCSS runs, causing the filename hash to not match the actual served content. When HTML templates change (like the reinvent page) but CSS source doesn't, PurgeCSS output changes while the filename stays the same. This causes CloudFront to serve stale CSS cached for up to 1 year. This commit adds a comment to tailwind.config.js to force Webpack to regenerate the CSS with new content, which causes Hugo to compute a new fingerprint hash. The new filename will not be in CloudFront's cache, forcing fresh content to be served. This is a temporary workaround. See #16274 for the proper long-term architectural fix. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
CamSoper
force-pushed
the
CamSoper/cloudfront-css-invalidation
branch
from
7982a40 to
254b3ab
Compare
Collaborator
|
Your site preview for commit 254b3ab is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-16275-254b3aba.s3-website.us-west-2.amazonaws.com. |
jkodroff
approved these changes
Oct 15, 2025
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
Adds a comment to
theme/tailwind.config.jsto force CSS regeneration, which busts the CloudFront cache that was serving stale CSS for the reinvent page.Problem
The reinvent page (https://www.pulumi.com/reinvent) was not displaying correctly in production because the CSS class
-translate-y-1/2was missing from the served CSS file.Root cause: The build process fingerprints CSS before PurgeCSS runs, causing CloudFront to cache CSS with a filename that doesn't match the actual content. When the reinvent template was added, PurgeCSS output changed (to include the new class), but the filename hash stayed the same because the source CSS didn't change.
CloudFront was serving a 20+ hour old cached version of
bundle.34a92c....cssthat was generated before the reinvent template existed.Solution
This PR adds a comment and unused class to
tailwind.config.jsto force Webpack to regenerate the CSS with new content. This causes Hugo to compute a new fingerprint hash, resulting in a new filename that CloudFront has never cached.When this deploys:
bundle.<NEW_HASH>.cssLong-Term Fix
This is a temporary workaround. The proper architectural fix is tracked in #16274, which proposes:
Testing
Files Changed
theme/tailwind.config.js- Added cache-bust comment with reference to Fix CSS fingerprinting to happen after PurgeCSS #16274🤖 Generated with Claude Code
Co-Authored-By: Claude noreply@anthropic.com