Empty SSR data on deployments without refresh

[huumn]

We are still getting stale caches when we deploy new code. I have to close and reopen the PWA and I have to refresh in browser otherwise I'm served old pages.

[huumn]

We really need to figure this out. It's making me shy with deployments because the whole client side goes stale until it's refreshed.

[ekzyis]

afaik, we used to nuke the whole cache on deployments but can't find that code anymore

[huumn]

I think what's happening is the build manifest and pages are getting cached on both the client and in the CDN ... so if there's any attempt to revalidate after deploying, it comes back as valid from the CDN.

So when we ship a new release there's nothing to let the client know they're fetching old files/data because the manifest points to old files and old files point to the manifest.

nope, so wrong

[huumn]

This might be the issue vercel/next.js#51823

not it

[huumn]

This appears to be a bug in nextjs. If it for some reason isn't a bug or they don't want to fix it, we will need to figure out a hack around it ... either profiling responses in the service worker or removing the header (which might have unexpected consequences).

vercel/next.js#56852