shields.io badge shows prerelease version; should show latest stable version

[sophiajt]

The CSV package (https://crates.io/crates/csv) currently shows both of these at the same time:

It seems the beta thing may be confusing crates.io to not show the correct Cargo.toml line? I'm not sure, but figured it was worth mentioning.

[sgrif]

There's an argument for either the badge or the Cargo.toml line being correct. We should probably decide whether we want to ever consider pre-release versions to be the "latest" version or not.

[carols10cents]

We decided in #577 not to recommend pre-release versions, so the shields.io badge should be changed to match the Cargo.toml snippet.

[locks]

This is actually a symptom of the problem described in #654, so we will track it there. Thanks for reporting!

[FabijanC]

Isn't this still an issue? E.g. consider this shields.io badge from the URL https://img.shields.io/crates/v/blockifier:

And consider these versions:
https://crates.io/crates/blockifier/versions

Shouldn't the badge show 0.5.0?

[Turbo87]

yes, but that is an issue on the shields.io side. https://crates.io/api/v1/crates/blockifier returns:

max_stable_version: "0.5.0"
max_version: "0.8.0-rc.1"

which shields.io could use to display 0.5.0 instead.

[FabijanC]

Thanks for pointing this out! I see there is an open issue on their side: badges/shields#8666