fix(lock): Use more accurate 'highest, rather than 'latest' - #17317
Merged
Conversation
rustbot
added
A-cli
Collaborator
|
r? @weihanglo rustbot has assigned @weihanglo. Use Why was this reviewer chosen?The reviewer was selected based on:
|
weihanglo
approved these changes
Aug 5, 2026
Member
There was a problem hiding this comment.
Makes sense. Some other package managers also use highest. Even our current doc uses highest.
Generally, Cargo prefers the highest version currently available.
https://doc.rust-lang.org/nightly/cargo/reference/resolver.html#version-numbers
rustbot
removed
the
S-waiting-on-review
This was referenced Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR try to resolve?
Using "latest" is already inaccurate because patches for previous versions can be released. With min-publish-age adding a time dimension, using "latest" becomes a non-starter.
So instead use "highest". We could have used "maximum" but "highest" felt nicer to me for some reason.
This is part of #17009
How to test and review this PR?