Zack TannerandJiachi Liu dd44191118 fix root page revalidation when redirecting in a server action (#64730) ...

When a server action triggers a redirect, we're incorrectly applying a
refresh marker to the segment they were on, rather than the segment they
were being redirected to. As a result, when revalidation occurs (via
`revalidateX` or `router.refresh()`), the top-level segment would be
replaced with data for an incorrect segment.

For example, if triggering a redirect action from `/redirect` to `/`,
the router state tree would save a reference to `/redirect`. The next
time a refresh or revalidate happens, it'd refresh the segment data for
`/redirect` instead of `/`.

Fixes #64728


Closes NEXT-3156

2024-04-23 17:34:14 +02:00

..

@dialog

…

@interception

fix revalidation/refresh behavior with parallel routes (#63607)

2024-03-28 12:59:27 +00:00

catchall

…

components

fix refreshing inactive segments that contained searchParams (#64086)

2024-04-04 23:44:54 +00:00

detail-page

…

dynamic

…

dynamic-refresh/[dynamic]

fix refreshing inactive segments that contained searchParams (#64086)

2024-04-04 23:44:54 +00:00

nested-revalidate

fix revalidation/refresh behavior with parallel routes (#63607)

2024-03-28 12:59:27 +00:00

redirect

fix root page revalidation when redirecting in a server action (#64730)

2024-04-23 17:34:14 +02:00

redirect-modal

…

refreshing

fix refreshing inactive segments that contained searchParams (#64086)

2024-04-04 23:44:54 +00:00

actions.ts

fix root page revalidation when redirecting in a server action (#64730)

2024-04-23 17:34:14 +02:00

default.tsx

…

layout.tsx

fix revalidation/refresh behavior with parallel routes (#63607)

2024-03-28 12:59:27 +00:00

page.tsx

fix root page revalidation when redirecting in a server action (#64730)

2024-04-23 17:34:14 +02:00