In Next 15.2.1 `revalidate` property was removed from `ctx` and `data.revalidate` should be used instead

[AyronK]

Brief Description of the Bug
A clear and concise description of what the bug is.

In Next 15.2.1 revalidate property was removed from ctx and data.revalidate should be used instead. This leads to all entries having default staleAge of exactly one year.

vercel/next.js@6a1b633

Severity
[Critical]

Frequency of Occurrence
[Always]

Steps to Reproduce
Provide detailed steps to reproduce the behavior, including any specific conditions or configurations where the bug occurs:

1. Use for example redis-string cache handler on Next 15.2.1 and compare the TTL with Next 15.2.0 or lower. It gets an extra year.

Expected vs. Actual Behavior
ctx.data.revalidate should be used to calculate TTL instead of ctx.revalidate

Screenshots/Logs
If applicable, add screenshots or error logs to help explain your problem.

Next 15.2.0

{
	"lastModified": 1743067428332,
	"lifespan": {
		"expireAge": 283, // correct 
		"expireAt": 1743067711, // correct 
		"lastModifiedAt": 1743067428, // correct 
		"revalidate": 189, // correct 
		"staleAge": 189, // correct 
		"staleAt": 1743067617 // correct 
	},
	"tags": [
		"ga::search-{\"query\":\"*\",\"subset\":\"category:='Kampagner#Fast lav pris'\",\"filterBy\":\"\",\"sortBy\":\"\",\"page\":null,\"pageSize\":24}"
	],
	"value": {
		"kind": "FETCH",
		"data": {
			"headers": {
				"content-type": "application/json; charset=utf-8",
				"date": "Thu, 27 Mar 2025 09:23:48 GMT",
				"request-context": "appId=cid-v1:9c14f46e-c7d4-41eb-b46b-ba886096fb7d",
				"server": "Kestrel",
				"transfer-encoding": "chunked"
			}
		}
	}
}

Next 15.2.1

{
	"lastModified": 1743068361456,
	"lifespan": {
		"expireAge": 47304000, // extra year
		"expireAt": 1790372361, // extra year
		"lastModifiedAt": 1743068361,
		"staleAge": 31536000, // extra year
		"staleAt": 1774604361 // extra year
	},
	"tags": [
		"ga::search-{\"query\":\"*\",\"subset\":\"category:='Kampagner#Fast lav pris'\",\"filterBy\":\"\",\"sortBy\":\"\",\"page\":null,\"pageSize\":24}"
	],
	"value": {
		"kind": "FETCH",
		"data": {
			"headers": {
				"content-type": "application/json; charset=utf-8",
				"date": "Thu, 27 Mar 2025 09:39:20 GMT",
				"request-context": "appId=cid-v1:9c14f46e-c7d4-41eb-b46b-ba886096fb7d",
				"server": "Kestrel",
				"transfer-encoding": "chunked"
			}
		}
	}
}

Environment:

• OS: n/a
• Node.js version: [22.14.0]
• @neshca/cache-handler version: [1.9.0]
• next version: 15.2.1

Dependencies and Versions
List any relevant dependencies and their versions.

Attempted Solutions or Workarounds

 const { revalidate, tags = [], neshca_lastModified, value } = ctx;

        const lastModified = Math.round(neshca_lastModified ?? Date.now());

        const hasFallbackFalse = CacheHandler.#fallbackFalseRoutes.has(cacheKey);

        const lifespan = hasFallbackFalse ? null : CacheHandler.#getLifespanParameters(lastModified, revalidate || value?.revalidate);

Impact of the Bug
Critical, we can't upgrade Next version which has a vulnerability due to this issue.

Additional context
n/a

[AyronK]

I created a temporary workaround, this is a decorator that we wrap the CacheHandler with:

const DecoratedCacheHandler = CacheHandlerDecorator(CacheHandler);
module.exports = DecoratedCacheHandler;

/*
 * TODO: Remove this after issue gets patched in neshca/cache-handler
 * https://github.com/caching-tools/next-shared-cache/issues/1027
 */
function CacheHandlerDecorator(BaseClass) {
    return class extends BaseClass {
        async set(cacheKey, incrementalCacheValue, ctx) {
            await super.set(cacheKey, incrementalCacheValue, {
                ...ctx,
                revalidate: ctx.revalidate || incrementalCacheValue?.revalidate,
            });
        }

        get(...args) {
            return super.get(...args);
        }

        revalidateTag(...args) {
            return super.revalidateTag(...args);
        }

        resetRequestCache(...args) {
            return super.resetRequestCache(...args);
        }
    };
}

[AyronK]

I have just noticed that there is no support for Next15 yet... #969

[neilhem]

@AyronK thanks for a temporary solution. But I am getting such an error when trying to access statically rendered pages

[TypeError: result.toUnchunkedString is not a function]

[AyronK]

@neilhem we have already solved this problem in https://github.com/fortedigital/nextjs-cache-handler. It's related to buffer-string breaking change in Next15.

This part precisely https://github.com/fortedigital/nextjs-cache-handler?tab=readme-ov-file#3-buffer-string-decorator

[jnm733]

Same problem here! In recent versions all my cache entries have 1 hour of expiration time.
For now I'm stuck in Next.js 15.1.7 version

[JannikZed]

Hi guys, we created a new caching lib, for next.js 15 only and a different approach than this project here. You can try it out if you like: https://github.com/trieb-work/nextjs-turbo-redis-cache