Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Builds on #9030
Motivation
color-eyre was restricitvely pinned to 0.6.3 which produced conflicts in crate consuming zebra
The goal is to allow consumers using a zebra crate as a dependencies to compile.
Specifications & References
https://doc.rust-lang.org/cargo/reference/resolver.html#semver-compatibility
Solution
By removing the manifest's pin to a specific minor version of the dependency, we allow consumers to find matching dependencies between their dependencies.
Tests
Follow-up Work
Allowing consumers flexibility in the dependency set of this workspace will make it more consumable.
I think a reasonable policy might be:
"^n" for n > 0
and
"~0.m" where n == 0.
Fastidious (nightly) runs of
cargo update
will keep developers aware of how the ecosystem is evolving relative to zebra.