fix(ci): switch release.yml to actions-rust-lang/setup-rust-toolchain#150
Merged
Conversation
Same dtolnay/rust-toolchain regression as ci.yml — `cargo build` invokes rustup-init instead of cargo on the current runner images. Apply the same fix that unblocked ci.yml (#146). The v2.7.1/v2.7.2 release runs failed because of this; next tagged release will pick up the fix automatically via release-please.
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
Same dtolnay regression as ci.yml, now hit during release builds. The release-please workflow merged v2.7.1 → triggered release.yml → all 5 platform builds fail at
cargo buildwith the samerustup-initerror.Apply the same fix that unblocked ci.yml in #146.
Impact
Test plan
gh workflow run release.yml -f tag=v2.7.2if we want to retry the existing tag.