Freshness check doesn't take into account changes in workspace deps

[simoncozens]

I bumped a version of crate foo in [workspace.dependencies], and then used cargo-smart-release on all my creates. However, one of the crates, crate-A had no code changes; cargo-smart-release refused to publish it because it thought that it hadn't changed (even though its dependent version of foo had changed), and so didn't release a new version. The top-level crate then could not be published, because it no longer compiles - its data structures used the new version of foo and crate-A crate passed in a data structure using the old version of foo.

[Byron]

Thanks for reporting!

This is a known issue though, and related to #8 .

Generally, it isn't advisable to use Workspace Dependencies right now as this is entirely uncharted territory.