Looks like I cant reply to you due to comment depth, so I'll reply here. The reason for being able to push "breaking" changes into the codebase is for future c

Looks like I cant reply to you due to comment depth, so I'll reply here. 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.