This should resolve some quirks around publishing when bumping versions of those crates: in this case, trying to publish tower-layer before publishing tower, such that tower@0.5.0 doesn't yet exist at the time of trying to publish tower-layer.
There's no real reason to tie dev dependencies to a specific version, since we would expect dev dependencies to be used during local development, on a feature branch or master, or whatever, when package versions are potentially in flux.
Context
As stated in the PR title.
This should resolve some quirks around publishing when bumping versions of those crates: in this case, trying to publish
tower-layerbefore publishingtower, such thattower@0.5.0doesn't yet exist at the time of trying to publishtower-layer.There's no real reason to tie dev dependencies to a specific version, since we would expect dev dependencies to be used during local development, on a feature branch or
master, or whatever, when package versions are potentially in flux.