Hi, if I use the contract_requiring_verification_published webhook lets say I have the following scenario: 1. consumer contract asks for fields that dont yet exist in provider 2. contract is published 3. webhook verifies it 4. verification fails 5. when we run the consumer pipeline again, the contract has not changed, so it will never be verified again ? 6. provider implements the new field how does the contract get re verified for the new provider version? I'm sorry if this is a stupid question. I don't want the webhook to simply trigger every time a contract is published whether it changes or not because that would be excessive. I guess I am wrong about step 5, it should be verified again when a new version of the provider is built, but if I don't see this behaviour, what has gone wrong?

That's what a regular provider build is for. You would setup the selectors to verify the usual pacts. If the pact in question is a feature branch, you would use WIP pacts to pull in new contracts to check

Here are a number of useful hands-on labs that teach all of the key concepts: https://docs.pactflow.io/docs/workshops and https://docs.pact.io/implementation_guides/workshops

Thanks, do you know how the

${pactbroker.providerVersionBranch}

var is set? I am using this one for the verification that happens when the Pact file changes. The version of the provider in UAT would be on the develop branch and the version in prod would be on the master branch but how can my Pact broker know this?

var is set? I am using this one for the verification that happens when the Pact file changes. The version of the provider in UAT would be on the develop branch and the version in prod would be on the master branch but how can my Pact broker know this?

It knows this, because you use your provider should be recording deployments to the environments it is deployed to