fix: use hardcoded checksum for minisign verification#16
Merged
ramonclaudio merged 2 commits intomainfrom Sep 7, 2025
Merged
Conversation
The minisign releases provide .minisig signature files, not .sha256 checksums. This fix uses a hardcoded SHA256 checksum to verify the minisign binary download since the .sha256 file doesn't exist at the expected GitHub URL.
Add concurrency groups to CI and Security workflows to prevent duplicate runs when PRs are created and merged. The workflows will now cancel in-progress runs when new commits are pushed, saving CI resources.
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
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
Fixes the failing publish workflow by using a hardcoded SHA256 checksum for minisign binary verification.
Problem
The publish workflow was failing with:
Investigation revealed that minisign releases don't provide
.sha256checksum files - they only provide.minisigsignature files for cryptographic verification.Solution
.sha256fileTesting
Verified the checksum by downloading the binary and computing its SHA256:
This fix will allow the publish workflow to successfully generate security artifacts (minisign signatures, GPG signatures, SBOMs, SLSA attestations) for all releases.