Repository navigation
Release 0.1.0 - #48
Merged
Merged
Conversation
Runs only on v* tags. Builds the Linux native executable and a JVM bundle, pushes the amd64 image to ghcr.io, joins it with an arm64 image when one was pushed for the same version, and drafts the GitHub release with checksums.
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
1 participant
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.
Sets the version to 0.1.0 and adds a release workflow.
.github/workflows/release.ymlonly runs when av*tag is pushed, so normal work costs no extra CI minutes. It:bin/hstore), and smoke-tests bothghcr.io/metacoglabs/hypergraph<version>,<major>.<minor>andlatestat the amd64 image plus an arm64 image, if one was pushed for that versionSHA256SUMSand generated notesThe arm64 image and the macOS binary get built on an Apple silicon Mac. Private repos have no free arm64 runners, and building a native image under emulation would eat a lot of minutes. The steps are in the new "Releasing" section of
docs/development.md. The README anddocs/operations/docker.mdnow say where the images and downloads are.I checked the version check, and ran the JVM bundle the way the workflow assembles it (init, load the example, check, version). Full
./mvnw installpasses.