hey a question for folks who know a thing or two about the broker webhooks. I've registered a webhook for the

contract_requiring_verification_published

event with url

<https://gitlab.com/api/v4/projects/${PROJECT_ID}/ref/${BRANCH}/trigger/pipeline?token=${TOKEN}&variables[PACT_URL]=>\${pactbroker.pactUrl}&variables[PACT_PROVIDER_VERSION]=\${pactbroker.providerVersionNumber}&variables[PACT_PROVIDER_BRANCH]=\${pactbroker.providerVersionBranch}

. For some reason when the broker triggers the pipeline it specifies a provider version number for the version of the provider at time of webhook creation and not for the latest main version of the provider. When the provider is deployed to an env it is recording the deployment with the git short sha for the commit and the latest main is months ahead of the version specified as

PACT_PROVIDER_VERSION

. I'm on version

2.102.2

of the broker. I have a sneaking suspicion that because the verification job does not have the correct provider version that it's unable to offer the pre-verifier support to contracts.

What does the triggered execution logs say? It will state the reason why the webhook fired in the first place.

Hey @Matt (pactflow.io / pact-js / pact-go). I'll find and dig in to them and share what I find. I've read through the documentation for

contract_requiring_verification_published

event and I wanted to ask if my understanding is correct. If a push of a contract contains the contents of a previously verified contract by the main provider it should be pre-reverified and not trigger the webhook.

It will be pre verified only for versions of the provider that have verified the same contents. This might be why it's triggering an OLED provider version. Perhaps it's deployed to an environment (even if an environment you don't use)

It only took me around 2 minutes to notice you intended to say old and not an acronym I was unfamiliar with😄