This first reverts the commit which bumped the versions to 1.0.0, then bumps the minor versions for the crates we know have in the past identified have received breaking changes.
If you go through the invidiual commits you can see how much churn a single version bump causes. Given how the interledger crate depends on all public api across crates, it does make me think if it would be best for this codebase to just have non-crates.io softer releases as the current dependency jungle is quite thick, with the re-exports the breakage will be difficult to track.
There's no hurry on my part, but this puts in code what I've been thinking recently and commenting on the issues.
CC: #668, #557
This first reverts the commit which bumped the versions to 1.0.0, then bumps the minor versions for the crates we know have in the past identified have received breaking changes.
If you go through the invidiual commits you can see how much churn a single version bump causes. Given how the
interledgercrate depends on all public api across crates, it does make me think if it would be best for this codebase to just have non-crates.io softer releases as the current dependency jungle is quite thick, with the re-exports the breakage will be difficult to track.There's no hurry on my part, but this puts in code what I've been thinking recently and commenting on the issues.