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
It seems like the documentation at http://io.itv.com/scala-pact/ is pretty out of date in terms of the latest published versions of this project. At the very least, misleading information should be cleaned up or removed.
By default, Scala-Pact does not allow you to publish pact files from SNAPSHOT versions of your project (but takes into account the pactContractVersion if set). This is because it can confuse pact brokers understanding of the latest contract.
Is this still accurate and will it cause problems even when tagging the consumer/provider with the branch when building off of CI? I ask because during CI we don't actually know what the next version of our application might be, it gets determined when the code is merged by providing a hint in the merge commit message (like "bump patch" or "bump minor"). So in our CI the best we can do is either set the contract version to a SNAPSHOT of what we think the next version would be (for example, if the current version is 1.0.0 we may do 1.0.1-SNAPSHOT+commit_sha), or we can just ignore the version entirely and do something like SNAPSHOT+commit_sha or even just commit_sha). Because I don't understand the details of this advice I'm not sure which of these options is best or which may cause problems.
It seems like the documentation at http://io.itv.com/scala-pact/ is pretty out of date in terms of the latest published versions of this project. At the very least, misleading information should be cleaned up or removed.
In particular I'm wondering about this snippet on http://io.itv.com/scala-pact/basics/sbt-commands.html:
Is this still accurate and will it cause problems even when tagging the consumer/provider with the branch when building off of CI? I ask because during CI we don't actually know what the next version of our application might be, it gets determined when the code is merged by providing a hint in the merge commit message (like "bump patch" or "bump minor"). So in our CI the best we can do is either set the contract version to a SNAPSHOT of what we think the next version would be (for example, if the current version is
1.0.0we may do1.0.1-SNAPSHOT+commit_sha), or we can just ignore the version entirely and do something likeSNAPSHOT+commit_shaor even justcommit_sha). Because I don't understand the details of this advice I'm not sure which of these options is best or which may cause problems.