Fix regional caching of tag cache #3504
Draft
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.
The regional tag cache was kind of broken.
If one tag was revalidated and some cache entry using it was updated, it would make other cache entry depending on that tag cache thinks that they were not stale.
It was very visible for customization update on a multi section website.
Still need some test (especially deployed), and ideally we'd need to find a way to test this in an e2e test.
This need to be backported to OpenNext.
One question here is : Do we prefer to have 1 cache entry per tag, or one per each incremental cache entry ?
Link to the OpenNext PR opennextjs/opennextjs-cloudflare#820