You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
we run into the problem, that the pact is "changed" after every dependency update, hence it has to be verified, because the metadata changes. I do understand, that metadata like the pact specification is important, but why is the pact-jvm version important?
We are not yet in the position of having the perfect flow, so my question is, if there is any way to exclude that field from the pact jsons, so we do not have a changing pact after every single dependency update?
Cheers
The text was updated successfully, but these errors were encountered:
you can't exclude it, it's part of the core library. the metadata shouldn't cause the pact to be re verified, you possibly have other random data or your workflow is set to verify on contract published and not contract requiring verification publish
Hi,
we run into the problem, that the pact is "changed" after every dependency update, hence it has to be verified, because the metadata changes. I do understand, that metadata like the pact specification is important, but why is the
pact-jvm
version important?We are not yet in the position of having the perfect flow, so my question is, if there is any way to exclude that field from the pact jsons, so we do not have a changing pact after every single dependency update?
Cheers
The text was updated successfully, but these errors were encountered: