next.js

a33edde8 - Server actions should not read stale data after calling `revalidate*` (#76885)

Server actions should not read stale data after calling `revalidate*` (#76885) When a server action calls `revalidateTag`, or `revalidatePath` for the current route, and subsequently reads the cached data in the action itself (before rendering), we need to ensure that we don't return stale data for the affected `"use cache"` functions and/or `fetch` calls. Previously, this was only guaranteed for the rendering phase after the action. closes NAR-116