{{ message }}
docs: preserve static routes during Cache Components adoption - #98275
Draft
aurorascharff wants to merge 1 commit into
Draft
docs: preserve static routes during Cache Components adoption#98275aurorascharff wants to merge 1 commit into
aurorascharff wants to merge 1 commit into
Conversation
Contributor
aurorascharff
force-pushed
the
codex/cache-components-static-contract
branch
from
September 4, 2026 20:34
a900545 to
7105e44
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
fetchandunstable_cachecaching can remain in place during Cache Components adoption.dynamic = 'force-static'ordynamic = 'error'instead of leaving them underinstant = false, which can move rendering to request time and reduce prefetched UI.Eval results
The updated
agent-047-adopt-cache-componentseval was attempted with Claude Opus 4.8:The local runner could not obtain Vercel OIDC credentials. These were infrastructure failures, so no eval criteria ran and no pass rates were produced.
Verification
pnpm --filter=next buildgit diff --check origin/canary...HEAD