Skip to content

v16.4.5

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 03 Nov 18:23
· 1 commit to main since this release
v16.4.5
9d12ae4
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Installation

npm install @mrjasonroy/cache-components-cache-handler@16.4.5

npm dist-tag: latest

Release notes

Two cache fixes, one opt-in option, and a stricter install check. Nothing to change in your
config. Release candidates 16.4.3-rc.5 and rc.6 carried these changes; they sort below 16.4.3 on
npm, so latest and ^16.4.3 installs never got them.

Install check. npm now refuses (ERESOLVE) to install this handler with a Next.js minor
other than its own. Upgrade the handler and Next.js together, and install with --save-exact.

Fixed

  • Page-cache entries now retain their request's first lookup timestamp, preventing a render
    completed after a tag invalidation from caching its old content as fresh. The production
    e2e matrix holds a render across invalidation, including two processes sharing Redis.
  • Data-cache reads enforce the exact render-start hard-expiry deadline in memory, Redis and
    outage fallback, including when rendering finishes between whole seconds.

Added

  • withCache(config, { useCache: "redis" }) shares plain "use cache" entries across instances.
    The default remains memory; explicit handlers.default takes precedence.

Changed

  • The handler is pinned to your Next.js minor. The next peer dependency (it was ^16.0.0) is now ~<major>.<minor>.0 of this release's own version (for example ~16.4.0 for 16.4.x, ~16.5.0 for 16.5.x). The package version follows Next.js, and the 16.5 releases remove the APIs deprecated in 16.4.3, so npm now refuses to install a handler whose minor does not match your Next.js (an ERESOLVE error) instead of pairing handler 16.5.x with Next 16.4; pnpm and Yarn warn. Each new Next minor moves the peer with it. Install with --save-exact and upgrade the handler and Next.js together.

What's Changed

Other Changes

  • docs: pin the package to the exact version for your Next.js by @mrjasonroy in #98
  • feat: pin the next peer dependency to the package's Next.js minor by @mrjasonroy in #99
  • docs: call out 16.4.3 as a major release under a patch number by @mrjasonroy in #100
  • fix: expire page renders that cross tag invalidation by @mrjasonroy in #104
  • chore: bump version to 16.4.3-rc.5 by @mrjasonroy in #105
  • DEVRES-4325: share plain use cache entries through Redis by @mrjasonroy in #106
  • chore: bump version to 16.4.3-rc.6 by @mrjasonroy in #108
  • test: gate cache invalidation on three kind pods by @mrjasonroy in #107
  • ci: pin runners to ubuntu-24.04 by @mrjasonroy in #110
  • fix: move post-16.4.3 changes out of the released 16.4.3 changelog by @mrjasonroy in #111
  • ci: record npm publishes on the Deployments page by @mrjasonroy in #101
  • docs: sweep the docs and add a start-here for people and agents by @mrjasonroy in #102
  • ✅ Next.js 16.4.5 - All tests passing by @mrjasonroy in #112

Full Changelog: v16.4.3...v16.4.5

💜 Thank you to everyone who contributed to this release!

Contributors

mrjasonroy
Assets 2
Loading