Repository navigation
Conversation
proof always said it was 0.1.0-dev. Releases set the version at build time now, and otherwise it's the one go install records in the binary (e.g. 0.1.0 for @v0.1.0, or a pseudo-version for a commit).
Servers that want proof in their CI shouldn't need Go for it, and they need a version they can pin. Tagging a version now builds proof for Linux, macOS and Windows and publishes the binaries in a GitHub release, with the version's section of the new CHANGELOG as its notes. The Releasing section of the hacking guide has the steps.
With the action, a server's workflow needs nothing but uses: nrepl/proof@v0.1.0 and the path to its profile. It downloads the binary of the release, and builds proof from source for anything that isn't a release, which is also how proof's own CI runs it against Babashka.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tagging a version builds binaries for Linux, macOS and Windows and publishes a release with that version's CHANGELOG section as its notes. The action downloads the release's binary when it's used at a tag, and builds proof from source otherwise. proof's own CI runs it with the eval checks only, as it tests the action, not Babashka.