fix(release): install minisign CLI fallback - #1926
Merged
Merged
Conversation
wgqqqqq
force-pushed
the
fix/release-minisign-cli-fallback
branch
from
July 31, 2026 08:45
ea0499c to
d1b00d6
Compare
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.
Summary
cargo install minisignfallback introduced in fix(release): fall back when minisign apt package is unavailable #1759; theminisigncrate is library-only and has no binary targetVerification
pnpm run check:github-configbash -n scripts/sign-release-assets.shgit diff --checkLocal limitation
Docker is installed but its daemon is not running locally, so the Linux executable test is delegated to the new
Shell Deploy ScriptsUbuntu CI step.