search

hedgehogqa / scala-hedgehog

Release with confidence, state-of-the-art property testing for Scala.
https://hedgehogqa.github.io/scala-hedgehog
Other
260 stars 23 forks source link

Semantic versioning releases #103

Closed charleso closed 4 years ago

charleso commented 5 years ago

I only want to do this if it's automated though. The easiest way would be to do another build/publish when a Git tag is added. That said, it would be great if we could add a PR process for adding a versioning so we can run mima.

charleso commented 5 years ago

I've added a tag-based release build for now, and released 0.1.0. I would still very much like a way to PR the releases and test against mima at some point

tmcgilchrist commented 4 years ago

What's the latest on setting up the SBT binary dependency? Should I be using a git sha as described in the README or pointing to a version?

charleso commented 4 years ago

At this point it doesn't matter. Every commit is still going to be published. I'll try to create semantic versions for every change too. The only thing that I haven't got yet that I would like is a PR-driven release to check binary compatibility.

I would probably use the semantic version as it's just easier to remember and track.

Kevin is also working on a Maven central sync which will be nice.

On Thu, 7 Nov 2019, 8:24 am Tim McGilchrist, notifications@github.com wrote:

What's the latest on setting up the SBT binary dependency? Should I be using a git sha as described in the README or pointing to a version?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/hedgehogqa/scala-hedgehog/issues/103?email_source=notifications&email_token=AAAHSU4BLMNR65Y6RBF56BTQSMYYHA5CNFSM4IK47TQKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEDIBB5A#issuecomment-550506740, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAHSU7AVG4FIHYVAM253CDQSMYYHANCNFSM4IK47TQA .