Bump num_enum to 0.6..=0.7
#857
Conversation
The transitive dependency `[email protected]` has MSRV of 1.67.0, while scylla has 1.66.0. So to maintain the current MSRV we specify a range that works for `Cargo.lock.msrv`. Curiously, without `Cargo.lock.msrv` is not able to resolve an appropriate version of `toml_edit`, and fails.
`cargo check --locked` errors due to the new requirements of `num_enum`. Running `cargo check` we see that we remove the dependency on `[email protected]` and are left with only `[email protected]`. This seems to be the only change to `Cargo.lock.msrv`, and should not cause problems.
|
I'm not sure it is a good idea to allow for two major versions. This will interact weirdly with the cargo resolver and could cause issues when used in a project where some dependencies (or the project itself) specifies I'd rather stick to only one version (bumping to just 0.6 sounds like less of a hassle). In the future, I'd like to get rid of the dependency altogether as it is not stable (<1.0, problematic for making this crate's API stable) but appears in the public interface (for Consistency and SerialConsistency) and doesn't offer too much functionality (we can implement TryFrom conversions manually). |
This PR bumps
num_enumfrom0.5and0.6to0.6..=0.7. The motivation for this is that[email protected]transitively allows for[email protected].Unfortunately another dependency of
scylla,ntest, still depends on[email protected]in its current release, but has bumped to0.20on master.ntestis however only adev-dependency, so I still think this will have upside for downstream users of scylla.Pre-review checklist
./docs/source/.Fixes:annotations to PR description.