Repository navigation
feat(update): publish and prefer compressed release binaries - #67
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 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.
Publish a gzip companion for each of the six lbctl binaries and include both forms in the SHA-256 manifest. The raw binaries keep their existing names for manual downloads and clients already installed. The updater chooses the platform-specific gzip asset when it appears in the manifest and validates both the archive and the extracted executable before replacement.
Local release builds measured 4.5–5.2 MB per archive, about 62% smaller than the original downloads. The updater regression covers raw and compressed releases, corrupted or truncated archives, and mismatches after extraction. The installer and download mirror changes are tracked in companion PRs.