Crates.io: Redirecting to the latest crate should only use non-yanked versions

Created on 20 Jan 2017  路  9Comments  路  Source: rust-lang/crates.io

Right now, if I visit https://crates.io/crates/quickcheck, I am redirected to the "This crate has been yanked" page (for version 0.4.2). However, we could just instead redirect to 0.4.1, the previous non-yanked version.

A-frontend C-bug

All 9 comments

related to #76

also related to (but distinct from) #145

This has been fixed by the changes in #592 !

Ok, this is not fixed completely. If I navigate to https://crates.io/crates/quickcheck directly, I correctly end up on the page for quickcheck 0.4.1.

HOWEVER if I search for quickcheck and click the search result link, I still end up with a page that says "this crate has been yanked" page that says 0.4.2 :( Something's not hooked up the way ember needs it to be :(

@carols10cents I'm still seeing this with actix right now

  1. last "stable" version is 0.7.10 (yanked)
  2. they just released 0.8.0-alpha.1
  3. suddenly the start page show "This crate has been yanked, but it is still available for download for other crates that may be depending on it."

@hoodie That's the expected behavior. crates.io/crates/actix shows the latest non-prerelease version, which has been yanked.

Scratch that, we should be redirecting to 0.7.9

This should be fixed by #1684 which I am deploying now

This appears to be fixed

Was this page helpful?
0 / 5 - 0 ratings