Fix Next.js segment prefetch cache key - #6983
Open
omercnet wants to merge 1 commit into
Open
Conversation
omercnet
force-pushed
the
fix/6969-next-prefetch-key
branch
from
August 28, 2026 20:10
f5b61aa to
cfb237c
Compare
omercnet
changed the title
Author
|
CI is waiting for maintainer approval because this pull request originates from a fork. Please approve the workflow run: https://github.com/anomalyco/sst/actions/runs/33207086592 |
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
1 participant
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
next-router-segment-prefetchin the Next.js CloudFront cache keyVerification
bun test platform/test/components/cloudfront.test.tsbun run typecheckbun run build:platformCloses #6969