Duplicate `wkt` crate entries in `Cargo.lock` when using `geozero v0.14.0`

[geoyogesh]

When geozero v0.14.0 is included as a dependency in a Rust project (either directly or transitively, e.g., via geoarrow-array), cargo tools (such as cargo llvm-cov, cargo check, or cargo build) report a warning about duplicate entries for the wkt crate in Cargo.lock.

The relevant section from Cargo.lock indicates that geozero v0.14.0 is the common dependency path leading to both wkt v0.11.1 and wkt v0.14.0:
warning[duplicate]: found 2 duplicate entries for crate 'wkt'
┌─ /path/to/your/project/Cargo.lock:XXX:YY
│
XXX │ ╭ wkt 0.11.1 registry+https://github.com/rust-lang/crates.io-index
XXX │ │ wkt 0.14.0 registry+https://github.com/rust-lang/crates.io-

[geoyogesh]

Hi, I'd like to add some specific context for this issue, as I'm running into this dependency conflict in my project.

I'm getting a warning[duplicate] from Cargo because my dependency graph requires two different major versions of wkt:

One part of my project dependencies (geoarrow-array v0.6.2) depends on wkt v0.14.0.

Another part depends on geozero v0.14.0, which in turn requires wkt ^0.11 (resolving to 0.11.1).

Because these are semantically incompatible, Cargo is forced to compile and link both versions, which adds to the compile time and final binary size.

Bumping the wkt dependency in geozero to 0.14.0 would resolve this conflict, which I suspect is common for anyone using geozero alongside the geoarrow ecosystems.

Thanks!

[kylebarron]

Looks like the version has been bumped but probably not released yet

geozero/Cargo.toml

Line 61 in fb2733c

wkt = "0.14.0"