Build Guance releases from tags - #2
Merged
Merged
Conversation
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Add a GuanceCloud-specific GitHub Actions workflow that publishes Linux binaries from Guance release tags.
Why
The upstream release workflow depends on Lightpanda-owned AWS, GHCR, and downstream repository credentials. Those dependencies prevent the GuanceCloud fork from reliably publishing usable binaries after syncing upstream changes.
Behavior
*-g*build native Linux x86_64 and aarch64 binaries.mainhistory.SHA256SUMS.0.3.6do not trigger this workflow.The first planned Guance tag is
0.3.6-g1after this workflow is merged tomain.Validation
actionlint .github/workflows/guance-release.ymlmainReleaseFast build and Zig release/debug tests pass on GuanceCloud Actions.