`cargo run --package` report `ambiguous`

[fan2nd]

Problem

I created a project named "esp32c6", clicked the run button close to main funtion in zed ide. then it report:

error: There are multiple `esp32c6` packages in your project, and the specification `esp32c6` is ambiguous.
Please re-run this command with one of the following specifications:
  esp32c6@0.1.0
  esp32c6@0.22.0

This ide just run cargo run --package esp32c6 --bin xxx. There is no problem in vscode because vscode run cargo run --package esp32c6:0.1.0 --bin xxx. I found esp32c6@0.22.0 is just a dependence in my project in Cargo.lock. I don't understand why cargo run treat it as a runnable package in my project.

Steps

No response

Possible Solution(s)

cargo run should only treat current project and its subproject as runnable package.

Notes

No response

Version

cargo 1.91.0 (ea2d97820 2025-10-10)
release: 1.91.0
commit-hash: ea2d97820c16195b0ca3fadb4319fe512c199a43
commit-date: 2025-10-10
host: x86_64-pc-windows-msvc
libgit2: 1.9.1 (sys:0.20.2 vendored)
libcurl: 8.15.0-DEV (sys:0.4.83+curl-8.15.0 vendored ssl:Schannel)
os: Windows 10.0.26200 (Windows 11 Professional) [64-bit]

[epage]

I have wondered about giving precedence to workspace members when there is ambiguity.

Hmm, I'm not hitting this with cargo run. Do you have reproduction steps?

I tried this with clap where clap has a transitive dev-dependency on an older version in the registry

$ git clone git@github.com:clap-rs/clap.git
$ cd clap
$ cargo check -p clap
$ cargo run -p clap
$ cargo tree -p clap
$ cargo tree -i clap
$ cargo clean clap
... cleans both
$ cargo update -p clap
error: There are multiple `clap` packages in your project, and the specification `clap` is ambiguous.
Please re-run this command with one of the following specifications:
  clap@4.5.39
  clap@4.5.51
$ cargo check -p clap@4.5.39
... panic
$ cargo run -p clap@4.5.39
error: package(s) `clap@4.5.39` not found in workspace `/home/epage/src/personal/clap`
$ cargo tree -p clap@4.5.39
$ cargo tree -i clap@4.5.39
error: package ID specification `clap@4.5.39` did not match any packages
help: there are similar package ID specifications:

  clap@4.5.51
$ cargo clean -p clap@4.5.39
warning: version qualifier in `-p clap@4.5.39` is ignored, cleaning all versions of `clap` found
     Removed 0 files
$ cargo update -p clap@4.5.39

• cargo update doesn't implicitly disambiguate like the other commands
  • Granted, most of the other commands are specified to only work with workspace members. cargo tree is the one exception.
• cargo check -p clap@4.5.39 panicking is panic when attempting to cargo doc -p a dev-dependency #11105
  • Should error like cargo run
• cargo tree -i clap@4.5.39 should work
• cargo clean is special because we don't track which build units would match a package id spec, only a name

EDIT: on the --features side, we have #3629

[epage]

Looks like we already have #12891, closing in favor of that