diff --git a/.changeset/fix-tag-expire-future-deadline.md b/.changeset/fix-tag-expire-future-deadline.md deleted file mode 100644 index 525fc34..0000000 --- a/.changeset/fix-tag-expire-future-deadline.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@leejpsd/nextjs-cache-handler": patch ---- - -Fix incremental `isTagStateExpired` so a future `expired` from `revalidateTag(tag, 'max')` no longer hard-misses every tagged entry for a year (#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. diff --git a/.changeset/seed-page-path-normalization.md b/.changeset/seed-page-path-normalization.md deleted file mode 100644 index bd6257f..0000000 --- a/.changeset/seed-page-path-normalization.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@leejpsd/nextjs-cache-handler": patch ---- - -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. diff --git a/.changeset/seed-route-scoped-keys.md b/.changeset/seed-route-scoped-keys.md deleted file mode 100644 index bed03ed..0000000 --- a/.changeset/seed-route-scoped-keys.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@leejpsd/nextjs-cache-handler": patch ---- - -`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` (#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. diff --git a/CHANGELOG.md b/CHANGELOG.md index eee430b..95ca4f2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,15 @@ # Changelog +## 1.0.2 + +### Patch Changes + +- [#17](https://github.com/leejpsd/nextjs-cache-handler/pull/17) [`44a0889`](https://github.com/leejpsd/nextjs-cache-handler/commit/44a08896d2b364f8da101e8ed0e52d014126bbd9) Thanks [@jeroendegloire](https://github.com/jeroendegloire)! - Fix incremental `isTagStateExpired` so a future `expired` from `revalidateTag(tag, 'max')` no longer hard-misses every tagged entry for a year (#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](https://github.com/leejpsd/nextjs-cache-handler/pull/21) [`3a57a0b`](https://github.com/leejpsd/nextjs-cache-handler/commit/3a57a0bad264e68c70387dbfa241155d4124b4f7) Thanks [@leejpsd](https://github.com/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](https://github.com/leejpsd/nextjs-cache-handler/pull/21) [`3a57a0b`](https://github.com/leejpsd/nextjs-cache-handler/commit/3a57a0bad264e68c70387dbfa241155d4124b4f7) Thanks [@leejpsd](https://github.com/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` (#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. + ## 1.0.1 ### Patch Changes diff --git a/package.json b/package.json index 0f0447c..4abb693 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@leejpsd/nextjs-cache-handler", - "version": "1.0.1", + "version": "1.0.2", "description": "Redis cache handler for Next.js 15/16 — the only one shipping both cacheHandler (ISR) and cacheHandlers ('use cache') with built-in compression, Redis Sentinel, and OpenTelemetry. Production-validated on multi-instance AWS: reconnect backoff, cross-instance tag invalidation, zero-downtime Redis failover.", "keywords": [ "next",