[nextjs][nextjs-app-router-osr] OSR App Router Template with Tag Revalidation Support#468
Open
MenKNas wants to merge 9 commits into
Open
[nextjs][nextjs-app-router-osr] OSR App Router Template with Tag Revalidation Support#468MenKNas wants to merge 9 commits into
MenKNas wants to merge 9 commits into
Conversation
…upport via tag revalidation
Contributor
📦 Package Size and Test Coverage Report
|
🦋 Changeset detectedLatest commit: 333773e The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
Description / Motivation
Summary
This PR introduces a new Next.js App Router template with OSR and tag revalidation out of the box.
It adds deterministic tag-based revalidation so published Sitecore changes refresh cached content reliably.
It also introduces two revalidation paths: a manual path for explicit tags and a webhook path that maps publish events to tags.
Finally, it adds dictionary fallback invalidation in the webhook flow to reduce stale dictionary-content cases.
As a side note, I decided to add two revalidation paths with distinct responsibilities:
/revalidate/)/revalidate/webhook)I found this separation of concerns more useful, but I’m happy to discuss if there is a strong reason to consolidate everything into a single route.
Testing Details
Verified end-to-end with local app + ngrok webhook URL: published Sitecore content, confirmed webhook calls hit
/api/revalidate/webhook, and confirmed updated content appears after refresh for both route and dictionary changes.Types of changes