First off, this crate is awesome. It is so close to being a does-what-you-want publish tool for cargo crates.

For this project though, we set our version numbers in the root workspace and cargo-smart-release doesn't seem to update things there. When the publish step comes, cargo fails because versions don't match.

If organizing workspaces like this is bad practice, I can change it. That's one major problem with large Rust projects and workspaces. There is no "do it this way" guide that actually works from start to publish.

I tried to reorganize the project to align with git-oxide. I moved the binary to the root and combined the package & workspace Cargo.toml, but it wasn't enough.

If this seems like a bug in cargo-smart-release vs how we structured our project, I'll gladly submit a PR if you can guide me to the part of the codebase I should start in.

Thanks again!