Cargo uses wrong dep version when dep is declared in [workspace.dependencies]

[f32by]

Problem

Steps
Workspace's Cargo.toml:

[workspace.dependencies]
arrayvec = { version = "0.7", features = ["serde"] }

Workspace member's Cargo.toml:

[dependencies]
arrayvec = { workspace = true }

1. Remove git and registry in ~/.cargo to force cargo re-download all deps.
2. Run cargo build
3. The member crate uses arrayvec-0.4.12 rather than arrayvec-0.7.1

Possible Solution(s)

Notes

Output of cargo version: cargo 1.55.0-nightly (3ebb5f1 2021-07-02)

[ehuss]

The ability to use workspace dependencies hasn't been implemented (see #8415). cargo build should print out several warnings to indicate that there are unrecognized fields:

warning: /ws/Cargo.toml: unused manifest key: workspace.dependencies
warning: /ws/foo/Cargo.toml: dependency (arrayvec) specified without providing a local path, Git repository, or version to use. This will be considered an error in future versions
warning: /ws/foo/Cargo.toml: unused manifest key: dependencies.arrayvec.workspace

When a dependency does not have a version, git, or path, Cargo treats it as version="*". As the warning mentions, this will be an error in the future.

Did those warnings not show up?

[f32by]

They did show up but I ignored them :( Thank you for clarification.

[ehuss]

Ok, I'm going to close as this is generally working as expected. I imagine the warning could become an error, as it has been around for 6 years.