-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Make the rust-version
error recommend cargo update --precise -p crate@ver
#10891
Make the rust-version
error recommend cargo update --precise -p crate@ver
#10891
Conversation
r? @ehuss (rust-highfive has picked a reviewer for you, use r? to override) |
Thanks! I'm concerned that this hint may be confusing for people using I wondering if maybe this hint to run It could also check |
eb4bea0
to
931bb6c
Compare
@ehuss Good point; done. |
b10e9ab
to
0b002e4
Compare
Fixing... |
2e44a65
to
df6e2cc
Compare
…precise ...` People encountering a dependency with a newer `rust-version` requirement may not know about `cargo update --precise`, or may consider alternate approaches that may be harmful (such as pinning with a `=` dependency). Provide specific guidance in the error message. If the user is using `cargo install`, suggest `cargo install --locked` instead.
Packages in the local workspace can't get updated this way; the user just needs to point to a different source, or otherwise update the package themselves.
df6e2cc
to
934e790
Compare
Thanks! @bors r+ |
…=ehuss Make the `rust-version` error recommend `cargo update --precise -p crate@ver` People encountering a dependency with a newer `rust-version` requirement may not know about `cargo update --precise`, or may consider alternate approaches that may be harmful (such as pinning with a `=` dependency). Provide specific guidance in the error message.
💔 Test failed - checks-actions |
@bors retry apt network error |
☀️ Test successful - checks-actions |
Update cargo 7 commits in 4fd148c47e733770c537efac5220744945d572ef..ce40690a5e4e315d3dab0aae1eae69d0252c52ac 2022-08-03 15:03:52 +0000 to 2022-08-09 22:32:17 +0000 - Make the `rust-version` error recommend `cargo update --precise -p crate@ver` (rust-lang/cargo#10891) - resolver docs: link to version requirements syntax full explanation (rust-lang/cargo#10946) - Bump os_info to 3.5.0 (rust-lang/cargo#10943) - Mark --timings=html unstable in the document (rust-lang/cargo#10941) - Mention that aliases are recursive (rust-lang/cargo#10935) - Test if reserved filenames are allowed in Windows (rust-lang/cargo#10322) - improve error message for `no such subcommand` (rust-lang/cargo#10924)
People encountering a dependency with a newer
rust-version
requirementmay not know about
cargo update --precise
, or may consider alternateapproaches that may be harmful (such as pinning with a
=
dependency).Provide specific guidance in the error message.