Conversation
The updater library (metal-stack/updater) looks for .sha512 release assets to verify downloaded binaries. Previously only .md5 files were generated, causing 404 errors during update check/do. Now both MD5 and SHA512 checksums are produced by the build target and included in release assets via the bin/cloudctl-* upload glob.
majst01
approved these changes
Apr 22, 2026
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
2 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.
The updater library (metal-stack/updater) looks for .sha512 release
assets to verify downloaded binaries. Previously only .md5 files were
generated, causing 404 errors during update check/do. Now both MD5 and
SHA512 checksums are produced by the build target and included in
release assets via the bin/cloudctl-* upload glob.