Conversation
theSoenke
approved these changes
Jan 19, 2026
Contributor
|
I noticed that with the recent changes, the release asset appears to have shifted from a standalone binary to a tar.gz archive. We currently use the following command in our CI/CD pipeline to fetch the binary: Could you clarify if this format change is intentional and permanent? If so, we will update our pipelines to handle the archive extraction. If not, I wanted to flag this as a potential issue with the release upload. |
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
3 participants
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.
fix(CLI): Unify asset uploading and release publishing steps to prevent duplicate releases.