-
Notifications
You must be signed in to change notification settings - Fork 7
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
funty 1.2.0 yanked #7
Comments
deku will have this same issue I assume. Since it still doesn't use bitvec v1 :( |
And confirmed, someone posted an issue: sharksforarms/deku#296 |
This is causing issues for me, our releases which were working are no longer installable. Please release a semver compatible version to fix the ecosystem. |
Following this issue closely. Can't install refinery_cli in my CI pipelines anymore due to this. |
Our build is also broken due to a transitive dependency on |
I had the same issue and Serhii gave me his |
@hanabi1224 Could you upload |
Also broke spacemeowx2/blflash#13 |
This version was yanked from crates.io after causing [breakage][1] in `bitvec 0.19.4`. However, `bitvec 0.22` was still [dependent][2] on it. [1]: ferrilab/funty#3 [2]: ferrilab/funty#7
"cargo install cargo-blflash" can install blflash 0.3.0, which requires funty 1.2.0 as a dependency. Funty 1.2 was yanked a while back (ferrilab/funty#7)
Also running into this problem with a dependency I cannot (currently) upgrade. Any comments/ideas @myrrlyn? |
I noticed funty 1.2.0 get yanked, however, one of my projects has a transient dependency on
bitvec 0.22
which requiresfunty="~1.2"
so cargo cannot resolve the version now. Is there any chance you can publish eitherbitvec 0.22.4
orfunty 1.2.1
to resolve the issue? Thanks!The text was updated successfully, but these errors were encountered: