I couldn’t find an example or a documented solution to managing breaking changes between consumers and providers After getting inspired by @Yousaf Nabi (pactflow.io) about a breaking change conversation prior, I’ve implemented a solution that allows us to dynamically handle breaking changes in our Pact tests with minimal intervention. Check out the full details in my blog post below, and the matching PR https://github.com/muratkeremozcan/pact-js-example-provider/pull/54 https://dev.to/muratkeremozcan/handling-pact-breaking-changes-dynamically-in-cicd-3dl4

I couldn’t find an example or a documented solution to managing breaking changes between consumers and providers

I don’t think there is an easy answer, and it really can depend on the type of change, and the way that teams interact / work and org manage that change and deploy the intention for pact is to tell you if you are making a breaking change or not, for the main/deployed/released consumers. if you don’t run those verifications, how do you know that the provider code you are changing, is compatible (or not) with their consumers, aside from your matching branch? are you proposing in this scenario, there is a full API breaking change being proposed by the providing team, and there will be an outage period whilst all services need to co-ordinate development? in your scenario, would all consumers need to publish pacts from the matching branch? does this only work, where you can get teams to agree to use matching branches (where there is high level of visibility and alignment between teams?)

there are two options, right? Either everyone accommodates the breaking change together, with matching PRs, or the provider has to make a backward compatible change and later deprecate it.