Skip to content

crates.io should encourage use of latest stable version, not alpha/beta versions #468

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

Closed
briansmith opened this issue Nov 15, 2016 · 3 comments
Labels
C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works E-help-wanted

Comments

@briansmith
Copy link

I just published ring 0.6.0-alpha so I could get some pre-release feedback. I expected that the page at https://crates.io/crates/ring would continue to say ring = "0.5.3" bit instead it says ring = "0.6.0-alpha". If somebody goes through the trouble to use the -alpha/-beta modifiers then they probably don't want the average user of their crate to use that version.

@alexcrichton
Copy link
Member

Agreed!

@steveklabnik
Copy link
Member

Especially given that you don't get a pre-release version without specifically selecting it; this seems quite consistent.

@steveklabnik steveklabnik added the C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works label Nov 15, 2016
elliotekj added a commit to elliotekj/crates.io that referenced this issue Mar 8, 2017
elliotekj added a commit to elliotekj/crates.io that referenced this issue Mar 8, 2017
carols10cents added a commit that referenced this issue Mar 11, 2017
@carols10cents
Copy link
Member

Fixed by #577!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement ✨ Category: Adding new behavior or a change to the way an existing feature works E-help-wanted
Projects
None yet
Development

No branches or pull requests

4 participants