funty 1.2.0 yanked

[hanabi1224]

I noticed funty 1.2.0 get yanked, however, one of my projects has a transient dependency on bitvec 0.22 which requires funty="~1.2" so cargo cannot resolve the version now. Is there any chance you can publish either bitvec 0.22.4 or funty 1.2.1 to resolve the issue? Thanks!

[wcampbell0x2a]

deku will have this same issue I assume.

Since it still doesn't use bitvec v1 :(

[wcampbell0x2a]

And confirmed, someone posted an issue: https://github.com/sharksforarms/deku/issues/296

[jessebraham]

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.

[okkero]

Following this issue closely. Can't install refinery_cli in my CI pipelines anymore due to this.

[PhilippGackstatter]

Our build is also broken due to a transitive dependency on [email protected]. We would be happy to see this fixed. Thank you!

[HedayatAbedijoo]

I had the same issue and Serhii gave me his cargo.lock and I could continue on my PC. But see the same bug on my new pull-request. one option could be adding cargo.lock to the source code by removing it from .gitignore

[hanusek]

@hanabi1224 Could you upload funty 1.2?

[benhadad]

Also broke https://github.com/spacemeowx2/blflash/issues/13

[memark]

Also running into this problem with a dependency I cannot (currently) upgrade.

Any comments/ideas @myrrlyn?