Best practices for backend releases while there are active sessions with stale frontend bundles
What are the best practices on how to deal with backend releases if there are still users using the app with stale frontend bundles. I've considered adding a custom header to the TRPC and check against it in the frontend but was wondering if there are any other solutions/resources about this topic around
3 Replies
there is no way to use git commit sha in some way?
try using something as a semver version or build number which you can make comparisons on (>, <, ==) and then you can branch out logic depending on the version. Also consider a strategy to get those stale bundles to be updated so you can stop supporting older versions over time. Not sure how though.
What I have had used in past is having a custom link component (can use the framework link underneath) but with a timeout of 24hrs after which the link would do a full page reload when pressed. Also I do same thing manual route navigations.