Yanking a crate should update its max_version

[alexcrichton]

If a crate has its max version yanked, it should update the max_version field to go back to the otherwise maximum version.

[huonw]

Suggestions for how this would handle yanking every version of a crate (e.g. publish a crate for the first time accidentally and then yank it, leaving no valid version at all)?

[alexcrichton]

That's a good question! I think that the returned value would just be null in that case as we just won't have a maximum version available.

[emk]

Right now, this bug makes it look like the Rust url crate is completely gone, leaving a big hole in the ecosystem. Apparently, this is not the case, but I was badly confused by it the other day.

[SimonSapin]

I just published url 0.4.0 to avoid confusion until this is fixed. It’s identical to 0.2.38, which is not compatible with 0.3.0 which was yanked. When the change from 0.3.0 lands again it’ll be 0.5.0. Version numbers are cheap.

[kamalmarhubi]

Surprising this issue has been around so long. Poor crates.io!