Repository navigation
fix(docker): package verified release binaries in images - #408
Merged
Merged
Conversation
Signed-off-by: overtrue <anzhengchao@gmail.com>
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.
The last successful emulated source image build took 2h22m, beyond the current 60-minute limit. This delays v0.1.37 even though its Linux binaries have already passed release verification.
Add an opt-in
use_release_binariesmode for stable version tags. It downloads the published static archives, checks SHA-256 and CPU architecture, and packages those exact binaries with the existing runtime tools and user. Each image architecture runsrc --versionduring the build before anything is pushed.Validation: all 1,988 workspace tests, formatting, Clippy with warnings denied, and actionlint passed. Archive-preparation checks cover valid files, bad checksums, wrong architectures, dynamic binaries, and invalid tags; all five tag-selection checks also passed. The v0.1.37 files used for those checks were verified against GitHub asset digests and SHA256SUMS.