Hi, many issues raised a problem when a new deployment happens which leads to a 200 status code for old client versions (old build id) leading to navigation with empty props and production issues when a 404 status code would be expected for a hard navigation to resync the client with the server's latest version:
I opened a pull request to address this:
https://github.com/vercel/next.js/pull/60968
Many issues mention this problem extensively:
https://github.com/vercel/next.js/issues/57207
https://github.com/vercel/next.js/issues/59612
https://github.com/vercel/next.js/issues/56222
https://github.com/vercel/next.js/issues/47516

Could you look at the pull request and consider it as a fix for our production problems ? Could we have an opinion on it ?