-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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] backport cargo #92839
[beta] backport cargo #92839
Conversation
Updates src/tools/cargo. cc @ehuss |
(rust-highfive has picked a reviewer for you, use r? to override) |
|
This comment has been minimized.
This comment has been minimized.
I followed this guide: https://forge.rust-lang.org/release/backporting.html#beta-backporting-in-rust-langcargo, but cannot figure out how the channel switch on CI works. 😞 |
This will need to wait until #92734 merges. After beta is branched (which was very recent), the release team has to push a PR through to update it before anything else can be merged to the beta branch. Sometimes that process is a little bumpy, as in this case. All tools must be functional on the beta branch, but RLS is currently broken. |
📌 Commit 5ecf27913fcc54dc7b01c24934cb74b8fe77c9d0 has been approved by |
5ecf279
to
57e5727
Compare
Should good to go, @ehuss. Take your time. No rush 🙂 |
Closing in favor of #93010. |
…ulacrum [beta] rollup This rolls up the following bumps onto the beta branch; no backports in this PR. * [beta] Bootstrap update rust-lang#92888 * [beta] backport cargo rust-lang#92839 r? `@Mark-Simulacrum`
backport cargo
2e4932801996a8799be8648a8858701e1ee8697a
for 1.59.0-beta[Beta] backport "Be resilient to most IO error and filesystem loop while walking dirs" cargo#10286