-
Notifications
You must be signed in to change notification settings - Fork 13.1k
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
Fix explanation of Cargo's behavior #25141
Conversation
`update`, which says ‘ignore the lock, figure out all the latest versions that | ||
fit what we’ve specified. If that works, write those versions out to the lock | ||
file’. | ||
file’. But, by default, Cargo will only look for versions larger than `0.3.0` | ||
and smaller than `0.4.0`. If we want to move to `0.4.x`, we’d have to update |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Worth mentioning semver/breaking changes in here somewhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not 100% sure. I'm so used to explaining every detail that this higher-level, ignore-the-details stuff is hard for me. I'm still trying to figure out what belongs and what doesn't.
Let's consider adding this kind of thing once the API evolution RFC lands.
r=me once the comment has been considered (doesn't have to be accepted). |
@bors: r=huonw rollup |
📌 Commit fc9bc77 has been approved by |
https://github.com/rust-lang/rust/pull/25080/files#r29634986
r? @huonw