Hi all I am seeing a weird behaviour:

can-I-merge

is using a latest version from branch

main

that is not the actual latest. And what is odd is that it has the actual latest version. As in it has there are verifications that use the actual latest version.

Ok, no worries. Any insights to share? We recently did hear a similar issue so wondering if it's perhaps something misleading or confusing we could address?

Hi Matt This was entirely my fault. I needed to debug a pipeline job that runs a

pact-broker delete-branch

on a merge request branch after it is merged. So I cloned a real service into my sandbox area. I did a number of merges without disabling the publishing of verification results on the sandbox project. Because we are still using v3 and have async and sync contracts we keep a list of alias per service

<service-name>-http

<service-name>-kafka

. The sandbox had the alias for the original project so those merges resulted in new provider versions associated with the original service. Those had no verification results. So when the

can-I-merge

ran on one of the consumers it stated correctly there were no verification results.