Open adamchalmers opened 2 years ago
Since it is a semver compatible version change, cargo should use the latest version of deepsize-derive
without requiring a version bump of deepsize
. You may have to use cargo update
or delete Cargo.lock
to unpin the old version of deepsize-derive
.
I've tested creating a new project that just depends on deepsize
version 0.2, and (according to cargo-tree
) it uses in deepsize-derive
0.1.2 without any changes.
Thank you for cutting the new deepsize-derive release (https://github.com/Aeledfyr/deepsize/issues/17), much appreciated. Could you please also cut a minor release for Deepsize which bumps its dependency on deepsize-derive from 0.1.1 to 0.1.2? That way when I use Deepsize, I will transitively pull in the newer deps.