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
This is a tricky one..
Provided a workspace, with the members foo, bar and syn.
foo
bar
syn
../syn
cargo ws version major will act on all the local crates foo, bar and syn. In this order:
cargo ws version major
The last tick there is the issue. cargo ws doesn't properly disambiguate between local crates and public ones.
cargo ws
The branch miraclx/crate-conflict is a stage for reproducing this experiment.
miraclx/crate-conflict
The text was updated successfully, but these errors were encountered:
Unfortunately, I think we need to implement the update logic with a proper TOML parser for this to be fixed.
Sorry, something went wrong.
Figured out a resolution for this, as well as a couple more edge cases in my fork.
No branches or pull requests
This is a tricky one..
Provided a workspace, with the members
foo
,bar
andsyn
.foo
depends on the localsyn
at path../syn
bar
depends on the public cratesyn
from crates.iocargo ws version major
will act on all the local cratesfoo
,bar
andsyn
. In this order:syn
crate.foo
crate.foo
's dependency on the localsyn
crate to the new version.bar
crate.bar
's dependency on the publicsyn
crate to the new version of the local crate.The last tick there is the issue.
cargo ws
doesn't properly disambiguate between local crates and public ones.The branch
miraclx/crate-conflict
is a stage for reproducing this experiment.The text was updated successfully, but these errors were encountered: