rust
/
rfcs
mirror of https://github.com/rust-lang/rfcs
1
0
Fork 0
Code Issues Releases Wiki Activity

fix(ref): Specify rust-version fallback when on pre-release

This commit is contained in:
Ed Page 2024-02-15 08:18:00 -06:00
parent d08e04f3a7
commit 9977612395
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
text/3537-msrv-resolver.md
View File

@ -760,7 +760,7 @@ This will be less optimal for workspaces with multiple MSRVs and dependencies un
Users can workaround this by raising the version requirement or using `cargo update --precise`.
When `rust-version` is unset,
we'll fallback to `rustc --version`.
we'll fallback to `rustc --version` if its not a pre-release.
This is primarily targeted at helping users with a
[`rust-toolchain.toml` file](https://rust-lang.github.io/rustup/overrides.html#the-toolchain-file)
(to reduce duplication)
@ -1144,6 +1144,9 @@ Some options include:
- `local` implies a `remote`
- `current` is like `latest` but a little softer and might work
Resolving with an unset `package.rust-version` falls back to `rustc --version` only if its a non-pre-release.
Should we instead pick the previous stable release (e.g. nightly 1.77 would resolve for 1.76)?
Whether we report stale dependencies only on `cargo update` or on every command.
See "Syncing `Cargo.toml` to `Cargo.lock` on any Cargo command".