From 3f0dc1349568be4c59b244ee455b2f413bb90648 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Fri, 24 Apr 2026 10:04:29 -0400
Subject: [PATCH] fix: fix loading state of flag

[dev] [Marfuen] mariano/fix-framework-update-status-stale-cache
---
 apps/app/src/hooks/use-framework-update-status.ts | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/apps/app/src/hooks/use-framework-update-status.ts b/apps/app/src/hooks/use-framework-update-status.ts
index f34804a4b..3305db8e5 100644
--- a/apps/app/src/hooks/use-framework-update-status.ts
+++ b/apps/app/src/hooks/use-framework-update-status.ts
@@ -27,7 +27,14 @@ export function useFrameworkUpdateStatus(
     },
     {
       fallbackData: options?.fallbackData,
-      revalidateOnMount: !options?.fallbackData,
+      // Always revalidate on mount, even when fallbackData is provided.
+      // fallbackData is only a fast first paint — without this, SWR treats
+      // the server-rendered snapshot as authoritative forever and skips the
+      // client fetch, so users don't see newly-available upgrades after the
+      // feature flag is flipped, after a sync on a sibling framework, or
+      // whenever the Next.js router cache serves a stale RSC. Short of
+      // signing out and back in.
+      revalidateOnMount: true,
       revalidateOnFocus: true,
     },
   );