Hi, I have a question about BiDirection Contract Testing. Steps I followed 1. I created OAS swagger.json file and published as provider contract with version 1.0.0 2. Ran can-i-deploy tool and recorded the deployment for the version 1.0.0 3. Generated the consumer contract which is compatible with provider contract 4.Published this consumer contract with version 2.0.0 5. Ran can-deploy-tool and it says consumer version 2.0.0 is compatible with provider version 1.0.0 6.Hence proceeded with deployment and recorded the deployment with consumer version 2.0.0 7.Now, I made a breaking change in provider contract (in OAS) and published to pact as version 1.0.1 8.Ran can-i-deploy and it says NO as provider contract 1.0.1 is not compatible with consumer version 2.0.0 9.I updated consumer executions to be inline with new provider change and published the consumer contract with version 2.0.1 10.In pact flow UI, I see that consumer version 2.0.1 is compatible with producer version 1.0.1 which is good 11.But when I run “can-i-deploy” it says NO as consumer version 2.0.1 is compared with producer version 1.0.0 instead 1.0.1 How can I proceed with deployment??

FYI For BDCT that is a PactFlow only feature, please use #CLS16AVEE for any specific questions. This question is about general can-i-deploy functionality, see the answer where you cross posted here: https://pact-foundation.slack.com/archives/C9UN99H24/p1679277036698909?thread_ts=1679267255.176679&cid=C9UN99H24