disallowed_methods falsely claiming "does not refer to a reachable function" (workspaces?)

Summary

In our codebase, we see the warning "does not refer to a reachable function" for one of the methods we have disabled in our clippy.toml using disallowed_methods.

I suspect that this is because the method is in a crate that is not a dependency of every crate in our worksapce? Or something.

Lint Name

disallowed_methods

Reproducer

Steps

git clone https://gitlab.torproject.org/tpo/core/arti
cd arti
git checkout f7b6a9d27408d07fafce9c90530177abe7b751ab
cargo clippy --locked --all-features --workspace --all-targets

Expected results

No warnings.

Actual results

warning: `rand::RngExt::random_range` does not refer to a reachable function
 --> /volatile/rustcargo/d/arti/clippy.toml:7:5
  |
7 |     { path = "rand::RngExt::random_range", reason = "Prefer tor_basic_utils::RngExt::gen_range_checked to avoid uncontrolled panics, or gen_range_infallible if applicable" },
  |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = help: add `allow-invalid = true` to the entry to suppress this warning
 
warning: `tor-geoip` (lib test) generated 1 warning

Version

rustc 1.96.0-beta.5 (a5a9a5438 2026-05-01)
binary: rustc
commit-hash: a5a9a5438ba8f6b83523031de99b15c12b44cea4
commit-date: 2026-05-01
host: x86_64-unknown-linux-gnu
release: 1.96.0-beta.5
LLVM version: 22.1.2

Additional Labels

No response

Reproduce the warning by checking out the stated arti commit and running the provided cargo clippy command. Start with the disallowed_methods lint and the rand::RngExt::random_range entry in clippy.toml; the work is done when valid workspace configuration no longer produces the false reachability warning, while genuinely invalid entries remain diagnosable.