From 1082a0fb4b4912350b81ffa31a053f1ecdff93f3 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Thu, 19 Nov 2026 04:01:04 +0000 Subject: [PATCH] Version Packages --- .changeset/tag-read-mode.md | 5 ----- CHANGELOG.md | 6 ++++++ package.json | 2 +- 3 files changed, 7 insertions(+), 6 deletions(-) delete mode 100644 .changeset/tag-read-mode.md diff --git a/.changeset/tag-read-mode.md b/.changeset/tag-read-mode.md deleted file mode 100644 index e01777d..0000000 --- a/.changeset/tag-read-mode.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"@leejpsd/nextjs-cache-handler": minor ---- - -New `tagReadMode` option for the `'use cache'` handler (#31). The default, `"scan"`, is unchanged: `refreshTags()` SCANs the namespace's tag markers into a local mirror on every request. Redis SCAN walks the whole keyspace regardless of the MATCH pattern, so that cost grows with the total number of keys in the database, not with the number of tags: about 20 ms per request at 20k keys and 65–170 ms at 100k against a local Redis. `tagReadMode: "on-demand"` turns the scan off; `get()` and `getExpiration()` instead `MGET` the markers for exactly the tags they are given (the entry's own tags plus the route's soft tags), one extra round trip per `get()`, which is how the singular handler and `getExpiration()` already worked. `tagPubSub` works in either mode. Thanks @royvou for the report and the proposal. diff --git a/CHANGELOG.md b/CHANGELOG.md index c08c78e..d60c792 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,11 @@ # Changelog +## 1.1.0 + +### Minor Changes + +- [#32](https://github.com/leejpsd/nextjs-cache-handler/pull/32) [`247f38f`](https://github.com/leejpsd/nextjs-cache-handler/commit/247f38f0087a1664ffba2bb41d069f6752875cad) Thanks [@leejpsd](https://github.com/leejpsd)! - New `tagReadMode` option for the `'use cache'` handler (#31). The default, `"scan"`, is unchanged: `refreshTags()` SCANs the namespace's tag markers into a local mirror on every request. Redis SCAN walks the whole keyspace regardless of the MATCH pattern, so that cost grows with the total number of keys in the database, not with the number of tags: about 20 ms per request at 20k keys and 65–170 ms at 100k against a local Redis. `tagReadMode: "on-demand"` turns the scan off; `get()` and `getExpiration()` instead `MGET` the markers for exactly the tags they are given (the entry's own tags plus the route's soft tags), one extra round trip per `get()`, which is how the singular handler and `getExpiration()` already worked. `tagPubSub` works in either mode. Thanks @royvou for the report and the proposal. + ## 1.0.6 ### Patch Changes diff --git a/package.json b/package.json index 05f8d3a..8be9da1 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@leejpsd/nextjs-cache-handler", - "version": "1.0.6", + "version": "1.1.0", "description": "Redis cache handler for self-hosted Next.js 15 and 16. Ships both cacheHandler (ISR) and cacheHandlers ('use cache'), with tag invalidation, deploy-time seeding, compression, Redis Cluster and Sentinel, and OpenTelemetry.", "keywords": [ "next",