The @10up/next-redis-cache-provider package reaches version 2.0.0, bringing the Redis-backed cache handler in line with modern Next.js architecture. This release introduces App Router support and adds compatibility with Next.js 15, making HeadstartWP a viable choice for teams building on the latest framework conventions.
App Router support
The headline change is support for the Next.js App Router. If you have been running your HeadstartWP frontend on the Pages Router and holding off on migrating, this update removes a key blocker by letting the Redis cache provider operate under the App Router’s caching model.
Next.js 15 compatibility
This release also adds support for Next.js 15, so you can upgrade your framework version without losing Redis-backed caching.
- App Router support — The cache provider now works with the Next.js App Router, not just the Pages Router.
- Next.js 15 support — Confirmed compatibility with the latest major Next.js release.
Upgrade notes
This is a major version bump for the package, driven by the App Router work. Review your cache handler configuration when upgrading to 2.0.0, and verify your caching behaviour against your chosen router before deploying to production.