The overall failure occurs, but the only interaction is green:

The consumer has added a header to the pact interaction, and the provider does not yet use the new header. So I expect the interaction to be forwards compatible. The webhook fires for event

Contract published that requires verification

and all signs point to the provider build to verify as passed. However it somehow gets this overall error?

It's worth noting (or not) that there's a WIP/Pending pact failing but that is irrelevant to this integration.

I'm using pact-go verifier. I have a webhook that passes

PACT_URL=

into the build, but i dont see the url in the logs:

executing verifier FFI with args [--consumer-version-selectors {"mainBranch":true} --consumer-version-selectors {"matchingBranch":true} --consumer-version-selectors {"deployedOrReleased":true} --hostname localhost --port 56162 --state-change-url <http://localhost:56162/__setup> --broker-url <https://redacted.pactflow.io> --provider-version 227d33ea99083b0a2aa9e5f17db735c31ce913d3 --provider-name RedactedService --publish --provider-branch main --loglevel trace --enable-pending --include-wip-pacts-since 2022-04-15T00:00:00Z]

ah - maybe i should explicitly pass it in then. i recall a handful of ruby cli automatically reading some pact env vars. i'll be that is what's impacting this q scratch one s head

this should probably move over to pact-go channel at this point. although i still dont quite understand how the original screenshot shows red but all interactions are green

what version on Pact Go are you on? There was a bug in the core that was recently fixed (in Dec, I think)

Based on the output above, it looks like it’s not one of the latest