-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
[beta] Prepare the 1.17.0 beta release #40484
Conversation
* Update stage0.txt to pending 1.16.0 release and current stable cargo rev from 1.16.0 * Update the release channel on CI to beta * Update the cargo submodule to master
r? @brson |
(rust_highfive has picked a reviewer for you, use r? to override) |
Note that if all goes according to plan we won't use buildbot to build this release, but rather I'll update rust-central-station to use prod secrets and we'll just magically get a new beta as soon as this merges. |
@bors r+ |
📌 Commit e20a0c2 has been approved by |
@bors: p=1000 (this is the beta release) |
⌛ Testing commit e20a0c2 with merge 9282f4b... |
💔 Test failed - status-appveyor |
It now follows rustc release trains
@bors: r=brson |
📌 Commit 0a27a87 has been approved by |
[beta] Prepare the 1.17.0 beta release * Update stage0.txt to pending 1.16.0 release and current stable cargo rev from 1.16.0 * Update the release channel on CI to beta * Update the cargo submodule to master
☀️ Test successful - status-appveyor, status-travis |
rustbuild: Don't hardcode 'nightly' for Cargo It now follows rustc release trains. I also had to land this commit on beta (rust-lang@0a27a87) before rust-lang#40484 could land, so this is basically just a forward port (if you will) of that commit to master.
1.16.0