@trieb.work/nextjs-turbo-redis-cache 1.11.0-beta.1 → 1.11.0

package/.github/workflows/ci.yml

@@ -7,7 +7,7 @@ on:
   pull_request:
     branches:
       - main
-      
+
 permissions:
   contents: write
   pull-requests: write
@@ -35,7 +35,6 @@ jobs:
           - next-test-app: next-app-16-0-3
             run-cache-components: true
 
-
     steps:
       - name: Checkout code
         uses: actions/checkout@v6
@@ -110,7 +109,7 @@ jobs:
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           coverage-file: './coverage/lcov.info'
-      
+
       - name: Dry run the release
         if: github.event_name == 'pull_request'
         env:
@@ -118,4 +117,3 @@ jobs:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }} # NPM token for publishing
         run: |
           npx semantic-release --dry-run
-

package/.github/workflows/release.yml

@@ -48,6 +48,19 @@ jobs:
           NPM_CONFIG_PROVENANCE: 'true'
         run: pnpm exec semantic-release
 
+      - name: Check if current version is already published
+        id: version-check
+        env:
+          NPM_PACKAGE_NAME: '@trieb.work/nextjs-turbo-redis-cache'
+        run: |
+          VERSION=$(node -p "require('./package.json').version")
+          echo "version=$VERSION" >> "$GITHUB_OUTPUT"
+          if npm view "$NPM_PACKAGE_NAME@$VERSION" version --registry https://registry.npmjs.org/ >/dev/null 2>&1; then
+            echo "should_publish=false" >> "$GITHUB_OUTPUT"
+          else
+            echo "should_publish=true" >> "$GITHUB_OUTPUT"
+          fi
+
       - name: Exchange GitHub OIDC token for npm token
         id: npm-oidc
         env:
@@ -116,6 +129,7 @@ jobs:
           NODE
 
       - name: Publish to npm (Trusted Publishing)
+        if: steps.version-check.outputs.should_publish == 'true'
         env:
           NPM_CONFIG_PROVENANCE: 'true'
           NPM_DIST_TAG: ${{ github.ref_name == 'beta' && 'beta' || 'latest' }}

package/CHANGELOG.md

@@ -1,11 +1,30 @@
-# [1.11.0-beta.1](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.10.0...v1.11.0-beta.1) (2025-12-30)
+# [1.11.0](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.10.3...v1.11.0) (2026-02-16)
 
 
 ### Features
 
-* add Next.js 16.0.3 integration test environment and build artifacts for cache components ([f2b3088](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/f2b3088c5845865cb69e5ee691cd09ede5735119))
-* add Next.js 16.0.3 integration test environment and build artifacts for cache components ([01fb22a](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/01fb22a9ae0fbbb6fba44bb225ab46fdcc009a85))
-* cache components lab + Next.js 16.1.x support ([be2e9b3](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/be2e9b3b7af441df112fc83483994877a4415443))
+* release cache components ([#67](https://github.com/trieb-work/nextjs-turbo-redis-cache/issues/67)) ([815e66b](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/815e66bab21f58d77693cad2a9d73f95ff8e7d79))
+
+## [1.10.3](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.10.2...v1.10.3) (2026-01-12)
+
+
+### Bug Fixes
+
+* avoid overlapping redis reconnects ([#58](https://github.com/trieb-work/nextjs-turbo-redis-cache/issues/58)) ([56e3465](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/56e3465669bcf07fa5267226a98977cbddd5ca3d))
+
+## [1.10.2](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.10.1...v1.10.2) (2026-01-05)
+
+
+### Bug Fixes
+
+* export CreateRedisStringsHandlerOptions type ([#66](https://github.com/trieb-work/nextjs-turbo-redis-cache/issues/66)) ([48df99f](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/48df99f5f348a464b8af58a0fa46187522aa4688))
+
+## [1.10.1](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.10.0...v1.10.1) (2025-12-31)
+
+
+### Bug Fixes
+
+* trigger publish and only publish on change ([#64](https://github.com/trieb-work/nextjs-turbo-redis-cache/issues/64)) ([d2a72e9](https://github.com/trieb-work/nextjs-turbo-redis-cache/commit/d2a72e9bd203aab13578dfc196c778da64c5046e))
 
 # [1.10.0](https://github.com/trieb-work/nextjs-turbo-redis-cache/compare/v1.9.1...v1.10.0) (2025-12-27)
 

package/README.md

@@ -1,7 +1,7 @@
 # nextjs-turbo-redis-cache
 
 [![npm version](https://img.shields.io/npm/v/@trieb.work/nextjs-turbo-redis-cache.svg)](https://www.npmjs.com/package/@trieb.work/nextjs-turbo-redis-cache)
-![Turbo redis cache image](https://github.com/user-attachments/assets/98e0dfd9-f38a-42ad-a355-9843740cc2d6)
+![Turbo redis cache image](https://github.com/user-attachments/assets/4103191e-4f4d-4139-a519-0b5bfab3e8b4)
 
 The ultimate Redis caching solution for Next.js 15 and the app router. Built for production-ready, large-scale projects, it delivers unparalleled performance and efficiency with features tailored for high-traffic applications. This package has been created after extensibly testing the @neshca package and finding several major issues with it.
 
@@ -27,8 +27,12 @@ Tested versions are:
 - Nextjs 15.3.2 + redis client 4.7.0
 - Nextjs 15.4.7 + redis client 4.7.0
 - Nextjs 16.0.3 + redis client 4.7.0 (cacheComponents: false)
+- Nextjs 16.1.1 + redis client 4.7.0 (cacheComponents: false)
+- Nextjs 16.1.1 + redis client 4.7.0 (cacheComponents: true)
 
-Currently PPR, 'use cache', cacheLife and cacheTag are not tested. Use these operations with caution and your own risk. [Cache Components](https://nextjs.org/docs/app/getting-started/cache-components) support is in development.
+Currently PPR, 'use cache', cacheLife and cacheTag are not tested. Use these operations with caution and your own risk. [Cache Components](https://nextjs.org/docs/app/getting-started/cache-components) are supported experimentally (Next.js 16+).
+
+For Cache Components, see the "Cache Components handler (Next.js 16+)" section below.
 
 ## Getting started
 
@@ -256,6 +260,8 @@ Integration tests may have dependencies between test cases, so individual test f
 
 This package can be used as a Cache Components handler (Node.js runtime) for Next.js apps that enable Cache Components.
 
+This is experimental support and the Next.js Cache Components APIs may still change. We don't have a larger production project right now available to test this in real world conditions.
+
 ### Enable Cache Components + cache handler
 
 Install the package in your Next.js app:

package/dist/index.d.mts

@@ -170,4 +170,4 @@ type CreateCacheComponentsHandlerOptions = CreateRedisStringsHandlerOptions;
 declare function getRedisCacheComponentsHandler(options?: CreateCacheComponentsHandlerOptions): CacheComponentsHandler;
 declare const redisCacheHandler: CacheComponentsHandler;
 
-export { RedisStringsHandler, CachedHandler as default, getRedisCacheComponentsHandler, redisCacheHandler };
+export { type CreateRedisStringsHandlerOptions, RedisStringsHandler, CachedHandler as default, getRedisCacheComponentsHandler, redisCacheHandler };

package/dist/index.d.ts

@@ -170,4 +170,4 @@ type CreateCacheComponentsHandlerOptions = CreateRedisStringsHandlerOptions;
 declare function getRedisCacheComponentsHandler(options?: CreateCacheComponentsHandlerOptions): CacheComponentsHandler;
 declare const redisCacheHandler: CacheComponentsHandler;
 
-export { RedisStringsHandler, CachedHandler as default, getRedisCacheComponentsHandler, redisCacheHandler };
+export { type CreateRedisStringsHandlerOptions, RedisStringsHandler, CachedHandler as default, getRedisCacheComponentsHandler, redisCacheHandler };

package/dist/index.js

@@ -541,15 +541,16 @@ var RedisStringsHandler = class {
             error,
             killContainerOnErrorCount++
           );
-          setTimeout(
-            () => this.client.connect().catch((error2) => {
-              console.error(
-                "Failed to reconnect Redis client after connection loss:",
-                error2
-              );
-            }),
-            1e3
-          );
+          setTimeout(() => {
+            if (!this.client.isOpen && !this.client.isReady) {
+              this.client.connect().catch((error2) => {
+                console.error(
+                  "Failed to reconnect Redis client after connection loss:",
+                  error2
+                );
+              });
+            }
+          }, 1e3);
           if (this.killContainerOnErrorThreshold > 0 && killContainerOnErrorCount >= this.killContainerOnErrorThreshold) {
             console.error(
               "Redis client error threshold reached, disconnecting and exiting (please implement a restart process/container watchdog to handle this error)",
@@ -565,12 +566,9 @@ var RedisStringsHandler = class {
         });
         this.client.connect().then(() => {
           debug("green", "Redis client connected.");
-        }).catch(() => {
-          this.client.connect().catch((error) => {
-            console.error("Failed to connect Redis client:", error);
-            this.client.disconnect();
-            throw error;
-          });
+        }).catch((error) => {
+          console.error("Failed to connect Redis client:", error);
+          throw error;
         });
       } catch (error) {
         console.error("Failed to initialize Redis client");