-
Notifications
You must be signed in to change notification settings - Fork 645
Crate version in search results doesn't match version on crate page #2710
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
Labels
Comments
@rustbot modify labels: A-versions C-bug |
This was referenced Aug 21, 2020
I'm interested in working on this. @rustbot claim |
bors
added a commit
that referenced
this issue
Dec 22, 2020
models/version: Add tests for `Version::top()` function While this can be tested through API tests it's much more convenient to have a unit tests for this functionality. This PR is in preparation for fixing #2710, by introducing a `max_stable_version` property on the `crate` resource. r? `@jtgeibel`
This is a duplicate of #654 I think. |
bors
added a commit
that referenced
this issue
Jan 5, 2021
Clean up `TopVersions` code This PR cleans up the code that figures out the `highest` and `newest` versions of a crate in several ways. I hope that the commit list gives enough context on the individual changes. Primarily, this decouples the code from the `Version` struct, and it moves the `0.0.0` defaulting to the `encodable()` method of the `Krate` model, instead of performing that in the low-level code directly. Like #3067, this PR is also in preparation for resolving #2710. r? `@jtgeibel`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See for example with
clap
:Search Results
/crates/clap
The version on the search page is a beta, while the version on the crate page (/crates/clap) is the latest stable release.
The text was updated successfully, but these errors were encountered: