The reason for being able to push "breaking" changes into the codebase is for future consumption. We control the consumers, which verify that they are able to integrate.
When all consumers have had their contracts updated to be insync with that service, then that service is no longer breaking - even though it hasn't been changed.
Its basically a way of preventing inter-service blockers.
I must admit, I thought these kind of pipelines would have been a lot more commonplace than they appear to be.
Obviously this isn't the exact scenario you're in at the moment, but if you're big enough -- this is exactly what it'll be like.
Implement backwards compatible changes and implement tracking on the users of the old features you want to disable. When your tracking shows nobody is using the old features, delete them.
That is how we manage it.
How do you define what is considered the current version for each microservice in your application?