rami3l

@HeWhoHeWho Thanks for your response. Both of your scenarios are valid but are not relevant to your original problem of "updating components". The idea is that when `rust-analyzer` is installed...

@HeWhoHeWho Binaries existing under `~\.cargo\bin` DON'T mean these components are installed. Some of those, such as `rust-analyzer.exe`, are just links to rustup which dynamically dispatches to installed components such as...

@cachebag I would like to kindly ask @ChrisDenton for the global stance on the Rust toolchain in general (if there is any) but I personally don't have the impression of...

> For rustup itself, we don't "officially" support it but we do make a best effort to support common environments so I think fixing issue 1 is possible. We could...

> I'd like to go to 1.29.0 and drop curl and native-tls support. @djc That sounds... risky since there are still remaining problems in #3790, and I would originally expect...

> It's not obvious to me what problems/remaining risks you are referring to. As I understand it, the change to rustls by default has been pretty smooth and has not...

> Might be good to also write up a list of (notable) changes that we have on master right now to get a handle on what the release would look...

@djc I am really sorry for the unexpected delay, but here is the draft PR: https://github.com/rust-lang/rustup/pull/4513.

@djc @ChrisDenton I think we are pretty close to cutting a new beta; I'd love to see #4471 in it before doing so though. Do you have other remaining concerns?

@djc I think we can continue with the release process once all concerns in https://github.com/rust-lang/rustup/issues/4423#issuecomment-3410895530 has been addressed. Is your remaining bandwidth okay for the "static.rust-lang.org certificates" PR, or did...