Search page shows latest chronological version, not latest semver

[repnop]

As of the creation of this issue (2020-04-10) the search page for string-interner looks like this:

and directs you to the page for version 0.6.4. However, the latest version of string-interner is 0.7.1, which is detected and displays the warning banner at the top to redirect you to 0.7.1.

Perhaps this is caused by the... very awkward release dates? Somehow the latest release from a semver point of view is 0.7.1 but date-wise its actually 0.6.4

From crates.io:

Versions

    0.7.1 Sep 1, 2019
    0.7.0 Aug 7, 2018 yanked
    0.6.4 Sep 3, 2019
    0.6.3 Sep 19, 2017 yanked
    0.6.2 Aug 13, 2017 yanked

[jyn514]

Perhaps this is caused by the... very awkward release dates? Somehow the latest release from a semver point of view is 0.7.1 but date-wise its actually 0.6.4

Yes, that sounds like the cause. I don't see a great way to fix this since currently searches are done using SQL only. We could normalize the search results to the latest sem-ver version after already picking a crate to show, but I'm a little hesitant to do that without a long-term plan for improving search results.

[syphar]

small addition, coming from #1521 :

for performance reasons we already have the latest version denormalized into crates.latest_version_id.

This column should not contain the latest build, but the highest non-yanked version with docs (edit: I remembered that we also show latest versions without docs)

so clicking on a crate in the release-views always brings you to a view without go to latest version link

[jyn514]

I think this may have been fixed by #1521, but I don't have an easy way to check.

[syphar]

I think this may have been fixed by #1521, but I don't have an easy way to check.

not really, in #1521 we still order by release-time for the version. #1546 will fix it correctly IMHO

[syphar]

Fixed with #1546 and #1567