-
Notifications
You must be signed in to change notification settings - Fork 13.4k
[beta] Bump bootstrap compiler to 1.27.2 #52776
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
Conversation
|
This comment has been minimized.
This comment has been minimized.
You'll need to revert the cargo version change; we distribute cargo under the old versioning scheme. The date is correct I think, not certain though. r=me once Travis passes though. |
2707aed
to
1c5f883
Compare
@bors: r=Mark-Simulacrum |
📌 Commit 1c5f883 has been approved by |
@bors p=1 |
@bors p=2 |
⌛ Testing commit 1c5f883 with merge 90586ed436cf2a4ae145559ece4daa2ad4ca5943... |
💔 Test failed - status-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@bors retry |
…acrum [beta] Bump bootstrap compiler to 1.27.2 This PR bumps the beta bootstrap compiler to 1.27.2. * The original cargo version was wrong: the current one is not `0.28.0`, but `1.27.0` (since rust-lang/cargo#5083). [Should the forge be updated?](https://forge.rust-lang.org/release-process.html) * The updated `date` is the correct one for rustc, but the wrong one for cargo. *I think* that shouldn't cause any problem, but it's better to ask. r? @Mark-Simulacrum
☀️ Test successful - status-appveyor, status-travis |
This PR bumps the beta bootstrap compiler to 1.27.2.
0.28.0
, but1.27.0
(since Make cargo-the-binary version the same as the Rust version cargo#5083). Should the forge be updated?date
is the correct one for rustc, but the wrong one for cargo. I think that shouldn't cause any problem, but it's better to ask.r? @Mark-Simulacrum