cargo-release
cargo-release copied to clipboard
bumping dependent crate versions?
Say I have a crate B that depends on A:
if i run cargo release minor --package A, it correctly updates the dependencies part of B's Cargo.toml, but it doesn't bump and publish B's version. Is there a way to do this that I am missing?
We currently do not support this in part because we do not know what version to release B as.
For applying minor to all of them, #298 is somewhat related
i currently use release-plz for this and hoped to just move everything to cargo release but I understand that picking the version is not straightforward. Just an idea but maybe a prompt for it could provide some help?
anyways thanks for the awesome crate!
I was recently evaluating release-plz for a project and this bugged me. See https://github.com/MarcoIeni/release-plz/discussions/1019
https://github.com/epage/epage.github.io/issues/23 explores a way of solving this problem