This changes will require a new major release of the node and consequently will require a new major release of the SDKs to support the new node version.
On the positive side this will not impact consensus (no hard hard fork) and will not require change on the applications that uses the SDKs since the changes are under-the-hood, but anyway it will require to eventually update your node and the SDKs on your app with it. Also if you are relying on the API Gateway for your app this will affect you (btw, you should always use on your own infrastructure ) for live projects).
And now the plan.
The plan is to merge this change for the next scheduled release that will happen in a bit more than 2 weeks time (around the 18th of July), followed by a release of the SDKs (Js/Py/Go) and with the API Gateway being upgraded one week after on the 25th of July. This release will be the
v4.0.0 for the node.
Hopefully this will not be too disruptive for you, but if you have concerns please share them here so we can address them properly.