"no matching version" when bumping workspace root package if something depends on it

[bluss]

Project layout is like this:

.
├── Cargo.toml     # petgraph
├── serialization-tests
│   ├── Cargo.toml # petgraph-serialization-tests
│   ├── src
│   └── tests
├── src
...

Cargo.toml is the workspace root and has the following content:

[workspace]
members = ["serialization-tests"]

The member's dependency relation looks like this:

[dependencies]
petgraph = { path = "..", features = ["serde-1", "quickcheck"] }

Steps to Reproduce

1. cargo build in the root
2. Edit root Cargo.toml to bump patch version
3. cargo build in the root

Step (3) gives an error:

error: no matching version `= 0.4.5` found for package `petgraph` (required by `petgraph-serialization-tests`)
location searched: file:///some/path/to/the/crate
versions found: 0.4.6
consider running `cargo update` to update a path dependency's locked version

Expected Behaviour

Take the update of the root package's version in stride, because we are building it itself. Just update the version in the lock file and build.

Cargo Version

cargo 0.23.0-nightly (33250c48b 2017-09-09)

[alexcrichton]

I think this may be a result of #4127, although I'm not 100% sure. Certainly run into it before!

[stale]

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

• Is this still relevant?
• If so, what is blocking it?
• Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

[stale]

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!