docs: clarify unstable_cache cross-deployment persistence (#100983)
## Summary - clarify that `use cache` replaces `unstable_cache` for most use cases, while `unstable_cache` remains appropriate for non-`fetch` data that must persist across deployments - link the reported agent feedback: https://next-maintainer-agent.vercel.tools/agent-feedback/5665 ## Related guidance reviewed - `docs/01-app/03-api-reference/01-directives/use-cache.mdx` already recommends `unstable_cache` for cross-deployment persistence of non-`fetch` data - `docs/01-app/03-api-reference/01-directives/use-cache-remote.mdx` already documents the same exception for remote cache entries - `docs/01-app/02-guides/migrating-to-cache-components.mdx` already states that migrating `unstable_cache` is optional and explains the persistence difference ## Verification - `pnpm exec prettier --ignore-path .prettierignore --check docs/01-app/03-api-reference/04-functions/unstable_cache.mdx` - `pnpm exec eslint --config eslint.config.mjs docs/01-app/03-api-reference/04-functions/unstable_cache.mdx` - `pnpm lint` (blocked by nine pre-existing unused Turbo Tasks findings on canary) <!-- NEXT_JS_LLM -->
Showing
Please
register
or
sign in
to comment