Draft
Conversation
Merged
a1f598a to
16082e9
Compare
16082e9 to
4b4e95e
Compare
CodSpeed Performance ReportMerging #1875 will not alter performanceComparing Summary
|
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.
As per the announcement: https://blog.rust-lang.org/2025/03/02/Rustup-1.28.0.html#whats-new-in-rustup-1280
There is a breaking change in rustup 1.28 and we must now manually run
rustup toolchain installto replace the default toolchain with the toolchain specified intoolchain.tomlThe announcement provides a way to remain compatible with both.
But I'll just wait for rustup 1.28 to arrive in github actions images to avoid the compatibility hack, since in the longterm its easier to understand.