Add release pipeline for Runtime #453
Merged
Conversation
This file contains 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
mattjohnsonpint
approved these changes
Oct 11, 2024
mattjohnsonpint
deleted the
kevinm/hyp-2299-create-official-builds-for-the-runtime
branch
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.
Description
This PR adds a release pipeline for the Modus Runtime using GoReleaser. This pipeline runs automatically on every new tag with the pattern
'runtime/v*'.This pipeline generates the Go binary for six targets:
{linux,darwin,windows}-{amd64,arm64}. Each binary is then archived together with the README and LICENSE files into atar.gz(zipfor windows) file.GoReleaser will then create a GitHub release with the current tag, upload all the artifacts and optionally generate the changelog based on the new commits since the previous tag. We can explore automatic changelog generation at a later time.
Signing and notarizing binaries are out of the scope of this PR, and will be explored separately. The side-effect of this is for macOS at least, the first time someone downloads it and try to execute the binary, they will be prompted with a message saying "
modus_runtimecannot be opened because the developer cannot be verified".