hi, my team started exploring pactflow recently and have published our contracts. However, the discussion recently has been more towards what are the best practices of publishing our future contracts. We have broken it down into several scenarios; 1. Do we only publish contracts when there are changes? 2. Do we always publish contracts when the pipeline is triggered regardless of changes or not in the contract?

1. Always publish contracts from your builds 2. see (1)

hi @Matt (pactflow.io / pact-js / pact-go),thanks for the reply. That means, even though there is no changes in the contracts, we still publish it from the builds?

Yes. I'd you don't publish we won't know about the new app version so we won't know if that version is compatible with its collaborators. We also internally version pacts and if the content doesn't change the pact version won't, and existing verification results apply