We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
If we have multiple versions of a dependency e.g.
[dependencies] futures = { version = "0.3" } futures01 = { version = "0.1", package = "futures" }
cargo upgrade will apply renames to both:
[dependencies] futures = { version = "0.3.8", package = "futures" } futures01 = { version = "0.3.8", package = "futures" }
Note the first redundant package = "futures".
package = "futures"
This is also true if we have at least one rename in a workspace, e.g.
# a.toml [dependencies] cargo-edit = "0.7" # b.toml [dependencies] me = { version = "0.7", package = "cargo-edit" }
will be upgraded to
# a.toml [dependencies] cargo-edit = { version = "0.7.0", package = "cargo-edit" } # b.toml [dependencies] me = { version = "0.7.0", package = "cargo-edit" }
The text was updated successfully, but these errors were encountered:
#725 just re did things and we no longer share processing across a workspace, so this should be resolved.
Sorry, something went wrong.
No branches or pull requests
If we have multiple versions of a dependency e.g.
cargo upgrade will apply renames to both:
Note the first redundant
package = "futures"
.This is also true if we have at least one rename in a workspace, e.g.
will be upgraded to
The text was updated successfully, but these errors were encountered: