Server Actions, APIs, Redeploys
Unanswered
Pavement ant posted this in #help-forum
Pavement antOP
When using traditional API endpoints, we can version the API and use tests to make sure that API requests from past versions of the app are still handled correctly by new code.
My question is, what happens when we change the interface that's used by a server action and redeploy? Do old clients just need to be forced to refresh after every deploy, or is there some other way that migration of old clients works when using Server Actions?
My question is, what happens when we change the interface that's used by a server action and redeploy? Do old clients just need to be forced to refresh after every deploy, or is there some other way that migration of old clients works when using Server Actions?
1 Reply
@Pavement ant When using traditional API endpoints, we can version the API and use tests to make sure that API requests from past versions of the app are still handled correctly by new code.
My question is, what happens when we change the interface that's used by a server action and redeploy? Do old clients just need to be forced to refresh after every deploy, or is there some other way that migration of old clients works when using Server Actions?
If you are using vercel then this may help, https://vercel.com/docs/deployments/skew-protection, otherwise you may have the issue with server actions...