Use explicit Rust setup inputs - #150
Open
timkpaine wants to merge 1 commit into
Open
Conversation
Signed-off-by: Tim Paine <3105306+timkpaine@users.noreply.github.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
注册 for free
to join this conversation on GitHub.
Already have an account?
登录 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.
Pins actions-ext/rust/setup at functional commit 7d919b14e08dc1155a267dffbcc58260bdfdd63b. Plain Rust requests only the macOS ARM target when needed; Rust/WASM requests wasm32 explicitly and adds macOS ARM conditionally. Both templates install exact Cargo tool versions through the action, while generated Makefiles skip tools already present instead of forcing recompilation.
Rendered and actionlint-validated both variants for Python 3.10 through 3.13. Generated Rust subprojects and requirement targets also pass locally.