Locally dependent crates not being updated when running `cargo workspaces version`

[joepio]

First off: thanks for creating this!

I'm using this in a workspaces project, but noticed that it behaved a bit different from what I was expecting. I might be doing something wrong, or might have misinterpreted how this is used.

Anyways, what is happening is that when I ran cargo workspaces version patch the cargo.toml versions were properly updated, but not the local [depedencies] version numbers.
I have an atomic-lib crate, which the atomic-cli and atomic-server depend on. I want these dependencies to update too when I run cargo workspaces version patch.

I don't know if this behavior makes sense for others, or if this is easy to implement.

[pksunkara]

Yeah, that's because patches are automatically treated as updated because cargo defaults to ^. If you want to be exact, try --exact.