Upgrade workspace's crate version

[maxv-rust]

Hello,

I have a workspace where I have multiple crates: crate_a, crate_b, crate_c.

I have to put both version and path for the crates from my workspace into the Cargo.toml (to allow crates to be published at crates.io):

[package]
name="crate_c"
version="0.0.9"

[dependencies]
crate_a = { version = "0.0.5", path = "../crate_a" }
crate_b = { version = "0.0.7", path = "../crate_b" }

Unfortunately cargo upgrade doesn't work in that case.

I'm able to fix that maxv-rust@8b4bfa3 but I'm not sure if you're interested in that kind of changes.

Please let me know what is the best way to fix the issue:

• should I just open a PR with my changes (probably not) or
• should I explain the problem better or
• could you please suggest what will be the better approach to solve the problem.

Have a great day,
MaxV

[epage]

Let me see if I understand the steps

• Upgrade crate_a to 1.0.0
• Run crate_c $ cargo upgrade and expect it to change from pointing to crate_a 0.0.5 to 1.0.0?

Not a maintainer but I think thats understandable. Even better will be with my next steps after #482 where crate_a $ cargo set-version 1.0.0 will update crate_c for you.

[epage]

I'm a little uncertain about the proposed fix. I think it will leading to surprising behavior if make merge_dependencies aware of this.

Instead, I would expect the sync lock file and upgrade functions to check that its a path dependency and generate the appropriate Dependency.