Hi folks, where can I find information about Pact-broker usage strategies? Right now we're using a very simple strategy: - enablePendingPacts in providers - when a breaking change in pacts is needed, consumers must create a new feature Tag in Pact-broker. - providers set pact-tests to use the new feature tag. - after development is complete, pacts are published in the main Tag and providers set pact-tests to use the main tag. - finally, pacts in the feature Tag are deleted. (We aren't using either WIP or recording deployments or releases) (We don't use branch because this is not supported in all client libraries) What do you think about this strategy? Thanks!

Hi @Arístides Suárez, it sounds ok. If you enabled WIP pacts, you wouldn't need to update the provider tag each time, however.

Hi, @Beth (pactflow.io/Pact Broker/pact-ruby), thanks for answering. "Breaking change", I mean, even having enabled pending pacts, after modifying pacts the verification fails. I'm going to study WIP pacts as an option.

a "breaking change" in our docs means that you change the API in a way that is not backwards compatible with its consumers. It doesn't mean just that the pact fails.