feat(release): automate binary release on tag push#778
Open
rishupk wants to merge 1 commit intoredhat-developer:mainfrom
Open
feat(release): automate binary release on tag push#778rishupk wants to merge 1 commit intoredhat-developer:mainfrom
rishupk wants to merge 1 commit intoredhat-developer:mainfrom
Conversation
58c3be8 to
e45ea82
Compare
Signed-off-by: Rishabh Kothari <rkothari@redhat.com>
e45ea82 to
67caec2
Compare
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.
The release process was manual before. This automates it on tag push.
Each matrix runner now extracts the mapt binary from the built container image using podman cp and uploads it as mapt-linux-amd64 or mapt-linux-arm64. A new release job picks those up, generates a sha256 checksums file, and creates a GitHub Release with everything attached.
The flattened OCI tarball artifacts are gone. Instead, each runner pushes its own arch image directly, and the manifest job stitches them together. Three new Makefile targets support this: oci-push-amd64, oci-push-arm64, and oci-push-manifest.
Signed-off-by: Rishabh Kothari rkothari@redhat.com