fix(tools): verify cargo-binstall with pinned flag#87
Merged
Conversation
f0rr0
added a commit
that referenced
this pull request
Jul 2, 2026
* fix(tools): verify cargo-binstall with pinned flag (#87) * fix(release): resume tagged publish runs * fix(release): seed swift package release
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
cargo-binstallwith-VRoot Cause
cargo-binstall --versionis not the version flag for the standalonecargo-binstallbinary; it is parsed as an install option requiring a value. The source-install fallback used the generic--versionprobe, so CI installedcargo-binstall v1.19.1and then failed with an empty/mismatched version read.Validation
bash -n tools/dev/bootstrap-tools.shbash tools/policy/check-tooling-stack.shgit diff --checkcargo-binstall -Vreturns1.19.1whilecargo-binstall --versionfails as an install optionNote: the same main CI run also has a separate Windows native-runtime failure from repeated HTTP 502s while downloading libiconv; that appears to be an upstream transient source download failure.