Summary of the new feature / enhancement
Coming out of #1422 we discovered our build was using ms-stable which had the unintended side effect of pinning us to Rust 1.88. You'll note our use of msrustup (when available), it is Microsoft's tool for installing compliant internal Rust toolchains. This is used in our release pipeline, and can be used by Microsoft developers.
In June 2024, the ms-stable moniker (passed to msrustup) was retired and we were supposed to move to the moniker ms-prod to get updates. We didn't do that, so it has stayed at the equivalent of ms-prod-1.88. At the same time, it is highly recommended to take updates intentionally, hence that PR does a blanket switch from ms-stable to ms-prod-1.93.
It would be best for us to specify and re-use this value in one place. The most correct and canonical way to do that is with a rust-toolchain.toml file. However, we need to do this in a way that when msrustup isn't available (such as for community devs) everything continues to work without a hitch.
Proposed technical implementation details (optional)
No response
Summary of the new feature / enhancement
Coming out of #1422 we discovered our build was using
ms-stablewhich had the unintended side effect of pinning us to Rust 1.88. You'll note our use ofmsrustup(when available), it is Microsoft's tool for installing compliant internal Rust toolchains. This is used in our release pipeline, and can be used by Microsoft developers.In June 2024, the
ms-stablemoniker (passed tomsrustup) was retired and we were supposed to move to the monikerms-prodto get updates. We didn't do that, so it has stayed at the equivalent ofms-prod-1.88. At the same time, it is highly recommended to take updates intentionally, hence that PR does a blanket switch fromms-stabletoms-prod-1.93.It would be best for us to specify and re-use this value in one place. The most correct and canonical way to do that is with a
rust-toolchain.tomlfile. However, we need to do this in a way that whenmsrustupisn't available (such as for community devs) everything continues to work without a hitch.Proposed technical implementation details (optional)
No response