Restrict the bitvec->funty dependency to <=1.1

[nickelc]

Nom builds fail since the release of funty 1.2.
see #1283 / pull/1283/checks

Alternative would be to bump the version of bitvec to 0.21

[coveralls]

Coverage remained the same at 82.652% when pulling d915250 on nickelc:restrict-bitvec-funty into 28d18a6 on Geal:master.

[therealprof]

@nickelc Thanks for sharing this observation, I was just scratching my at this weird breakage and can confirm that restricting the funty version in my application Cargo.toml works.

[Geal]

thank you, I'm pushing a release right away

[nickelc]

Apparently this fixes the nom builds but not projects depending on nom :(

cargo up --dry-run
    Updating crates.io index
    Updating funty v1.1.0 -> v1.2.0
    Updating nom v6.1.0 -> v6.1.1
    Updating redox_syscall v0.2.4 -> v0.2.5

[therealprof]

@nickelc Hm, seems you're right... 😟 bitvec is the culprit pulling the version up and that can only be overridden by the application.

funty v1.2.0
└── bitvec v0.19.4
    └── nom v6.1.1

[nickelc]

nom 6.1.2 fixed it.

@Geal thank you

[Geal]

Yes, 6.1.1 was not enough, there was a small fix to add, now it works 🥳