Hi! I successfully worked my way through this tutorial (thanks for writing it!): https://docs.pactflow.io/docs/workshops/bi-directional/step1 I am using the dredd provider and mountebank consumer. I got everything working, including github automation and making contract-breaking changes to see the errors. I then decided to rebuild both projects with the latest version of npm modules since they were a year or two out of date. I succeeded with one exception: When I run can-i-deploy on the provider I get

No pacts or verifications have been published for version 9c9a30-master+9c9a30.SNAPSHOT.mika of pactflow-example-bi-directional-provider-dredd

I get this same message running locally or on Github. Strangely, Pactflow show that the provider was updated and I get a green check-mark I doubt this has anything to do with my npm module update. Rather I am really new to this and probably just making a noob mistake. I tried republishing the consumer, and setting the provider version in package.json to match. I still get the same thing.

My guess is one of the following: 1. You aren’t setting the flag to say the verification passed 2. Some version is not getting aligned (i.e. the version you’re checking is slighly different to the version you’re publishing (it looks like a SHA so probably not) Flags for (1)

[--verification-success], [--no-verification-success]                    # Whether or not the self verification passed successfully.
      [--verification-exit-code=N]                                             # The exit code of the verification process. Can be used instead of --verification-success|--no-verification-success for a simpler build script.

HI Matt, I didn't change the sample code between it working and not working, but I do see a line in buid.yml for "publish" that has this flag --verification-exit-code=0

That happens in a background process, the simple explanation is that it checks against deployed/released versions of consumers, as well as the main branch. I believe it does some others, but these are likely to cover the majority. When you run

can-i-deploy

you can be more explicit about what consumer pact versions to compare to