Skip to content

Version Packages - #22

Merged
leejpsd merged 1 commit into
mainfrom
changeset-release/main
Nov 13, 2026
Merged

leejpsd merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

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 44a0889 Thanks @jeroendegloire! - Fix incremental isTagStateExpired so a future expired from revalidateTag(tag, 'max') no longer hard-misses every tagged entry for a year (Incremental handler treats a future expired from revalidateTag(tag, 'max') as already expired #14). Hard invalidations (updateTag, single-argument revalidateTag) still apply the moment they are read, even on an instance whose clock is behind the one that wrote them.

  • #21 3a57a0b Thanks @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 a MISS. Routes whose path starts with /index were 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 3a57a0b Thanks @leejpsd! - seedBuildOutput and the seed CLI 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.key in .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 a MISS (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.

@leejpsd
leejpsd merged commit 65d23f2 into main Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant