fix(blog): refresh cached article pages after R2 updates - #50
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
This branch was successfully deployed
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
2 participants
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.
An n8n article refresh updates the R2 HTML, but Vercel continues serving the previously prerendered
/blog/[slug]page. The live pilot changed the R2 object while the public page remained a Vercel cache hit with the old paragraph.Regenerate article pages every 15 minutes and give their CDN responses the same 15-minute cache period with a one-minute stale window. This keeps static delivery while allowing published article edits to reach readers after revalidation.
Validation:
yarn lintpassed with four existing warnings in unrelated files.yarn test:buildpassed using the repository's test environment; Next.js reported a 15-minute revalidation period for/blog/[slug], and the generated HTML for the pilot article contained the refreshed text.