Don't specify explicit version for dev-dependencies

[alice-i-cecile]

Once this PR is merged, I intend to release taffy 0.2.

Testing the release currently fails:

alice@pop-os:~/Documents/Code/taffy$ cargo publish --dry-run
Updating crates.io index
Packaging taffy v0.2.0 (/home/alice/Documents/Code/taffy)
error: failed to prepare local package for uploading

Caused by:
failed to select a version for the requirement taffy = "^0.2.0"
candidate versions found which didn't match: 0.1.0
location searched: crates.io index
required by package taffy v0.2.0 (/home/alice/Documents/Code/taffy)

Removing the explicit version causes this to pass correctly. It's currently unclear how this worked before. EDIT: it never has :(

[alice-i-cecile]

@TimJentzsch, this was added in #165. Unfortunately, it doesn't seem compatible with actually publishing the crate, so I need to revert it.

[TimJentzsch]

My guess is it worked before because 0.1 was already published when I added it.

I think I fixed the version because of cargo-deny, hopefully we can make it work somehow.

alice@pop-os

I see you have good taste in operating systems :D

[nicoburns]

I think we can just add taffy to the skip list here in deny.toml:

[bans]
multiple-versions = "deny"
wildcards = "deny"
highlight = "all"
# Certain crates/versions that will be skipped when doing duplicate detection.
skip = [
    { name = "itoa", version = "1.0.2" }
]

https://embarkstudios.github.io/cargo-deny/checks/bans/cfg.html

[alice-i-cecile]

Looks like this is working successfully locally :) This should be disabling the check only for taffy itself. Per the docs, we would need to use skip-tree to disable checks for all descendants.