connectapi shouldn't be calling deprecated endpoints--when we deprecate endpoints that it uses, we'll make sure to check the Connect server version and call the correct endpoints accordingly, so that it only calls deprecated endpoints on older Connect versions where they aren't deprecated. The only circumstance where connectapi would hit a deprecated endpoint would be if you're pointing at a newer version of Connect but an old version of connectapi that doesn't know about the new, non-deprecated endpoints. So, when receiving a X-Deprecated-Endpoint response header, the recommendation to the user is to upgrade connectapi.
connectapishouldn't be calling deprecated endpoints--when we deprecate endpoints that it uses, we'll make sure to check the Connect server version and call the correct endpoints accordingly, so that it only calls deprecated endpoints on older Connect versions where they aren't deprecated. The only circumstance whereconnectapiwould hit a deprecated endpoint would be if you're pointing at a newer version of Connect but an old version ofconnectapithat doesn't know about the new, non-deprecated endpoints. So, when receiving aX-Deprecated-Endpointresponse header, the recommendation to the user is to upgradeconnectapi.