-
Notifications
You must be signed in to change notification settings - Fork 45
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
crates.io version 0.15.1
#484
Comments
Please upload a |
Thanks for the bug report! This was of course not the intention of the change in #453. From what I understand, it seems that making a 0.15.2 release without the semver breaking changes would fix this. I'll get onto that immediately. |
A 0.15.2. release has been made in #486 — it's identical to the 0.15.0 release and it is thus a safe semver-compatible target for people trying to install I'm sorry about the breakage! Lesson learnt: don't yank a crate if you don't offer a semver-compatible upgrade path to downstream users. I had not run into this corner-case before but now I know. |
This should be fixed now, please let me know if you see any other problems! |
All good on my end, thank you very much for the timely fix! |
As [textwrap 0.15.1 got yanked](mgeisler/textwrap#484), it caused some build issue [in the homebrew side](Homebrew/homebrew-core#116662), bumping the dependency to 0.15.2. Signed-off-by: Rui Chen <[email protected]>
Seems that
0.15.1
was removed from crates.io. Can we have a version that will be resolved by cargo when0.15.1
is specified inCargo.toml
?The text was updated successfully, but these errors were encountered: