Release artifacts(static binaries) to GitHub releases #41
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
Signed-off-by: House <[email protected]>
Signed-off-by: House <[email protected]>
Signed-off-by: House <[email protected]>
rakshitgondwal
approved these changes
Jul 3, 2024
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.
#24
This PR allows users to setup a release that can be triggered when a new git tag is created.
Creates a github release in the given owner/repo. This can allow users to upload artifacts to a different location without requiring to release with their source code.
Uploads artifact and its attestations. Artifact is in tar.gz format to accommodate for future use-cases(expand more than static binaries)
Artifact name and attestations include the target OS/Arch.
A flake.nix is generated for the artifact such that it can be downloaded and
nix run/nix profile install.PR also includes code to upload artifact to OCI as that was our initial goal. However, considering how public images in hosted registries don't allow unauthenticated requests- this has been put off. We might explore and build bsf specific functionality leveraging OCI as nix binary cache in future.