Repository navigation
Version Packages - #22
Merged
Merged
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
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@leejpsd/nextjs-cache-handler@1.0.2
Patch Changes
#17
44a0889Thanks @jeroendegloire! - Fix incrementalisTagStateExpiredso a futureexpiredfromrevalidateTag(tag, 'max')no longer hard-misses every tagged entry for a year (Incremental handler treats a futureexpiredfrom revalidateTag(tag, 'max') as already expired #14). Hard invalidations (updateTag, single-argumentrevalidateTag) still apply the moment they are read, even on an instance whose clock is behind the one that wrote them.#21
3a57a0bThanks @leejpsd! - Fix seeding of the root route on Next.js versions before 16.3.8. Those versions store and look up prerendered routes under Next's normalized page path, where/is/index, but the seed wrote the root route under/, so it was never read and the first request to the home page after a deploy was aMISS. Routes whose path starts with/indexwere also read from the wrong build files. The seed now uses the same normalization as Next for both the artifact path and the key.#21
3a57a0bThanks @leejpsd! -seedBuildOutputand theseedCLI now write prerendered App Router and Pages Router routes under the route-scoped key that Next.js 16.3.8+ records in each build artifact (routeCache.keyin.meta). From 16.3.8 the runtime never asks a custom cache handler for a bare pathname, so pathname-keyed seeds were written but never read and the first request after a deploy was still aMISS(seedBuildOutput writes pathname keys; Next 16.4+ Full Route Cache reads meta.routeCache.key #16). Builds from older Next.js versions carry no such metadata and are seeded under the page path as before; no option or flag is needed.