-
Notifications
You must be signed in to change notification settings - Fork 300
Rollback rustup 1.28 #1499
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Rollback rustup 1.28 #1499
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,15 @@ | ||
--- | ||
layout: post | ||
title: "Rolling back Rustup 1.28.0" | ||
author: The Rustup Team | ||
--- | ||
|
||
Due to unexpected impact to many CI systems not being ready for the new | ||
rustup-toolchain.toml behavior, we have rolled back the rustup [1.28.0] release. | ||
Rustup should self-update back to 1.27.1, and new installations will start to | ||
install 1.27.1 again. | ||
|
||
The Rustup team will follow up with a more concrete plan for rolling out the | ||
changes in 1.28, but we're mitigating impact through a rollback for now. | ||
|
||
[1.28.0]: /2025/03/02/Rustup-1.28.0.html |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I hope that we won't do a rollback as I think it would cause more issues than it would solve, but just a remark: I don't think that it even was possible to get ready without knowing the universal command, as the new install command didn't work before
1.28.0
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, happy for other phrasing, I just wrote basically a first pass here that seems acceptable if not great (as you say) :)