fix(info): default to local without explicit reg

[0xPoe]

What does this PR try to resolve?

close #16145

93c2c40 (#16358) shouldn't be an error; it should inspect the local package correctly.

The reason it is buggy is as follows: The default_registry function attempts to retrieve the default registry from the user's configuration; in this case, it is crates-io.

in src/cargo/ops/registry/mod.rs:210-248(get_source_id_with_package_id):

  (Some(reg_or_index), Some(package_id)) => {
      let sid = get_initial_source_id_from_registry_or_index(gctx,
  reg_or_index)?;  // crates-io
      let package_source_id = package_id.source_id();  // local path source
      // Check if they match or if one replaces the other
      if sid == package_source_id  // false: crates-io != path
          || is_replacement_for_package_source(gctx, sid,
  package_source_id)?  // false: no replacement for local path
      {
          (true, package_source_id)
      } else {
          (false, sid)  // <-- Returns this: "don't use local package, 
  search in registry"
      }
  }

In this PR, I modified the cargo-info to prefer the local package if the registry is not explicitly specified.

How to test and review this PR?

Check the unit test.

1. One case for reproducing the described issue. It shouldn't be an error. We should inspect the local package properly.
2. Another case specifies the registry configured in the config file to ensure we can search the registry correctly.

r? @ghost

[0xPoe]

🔢 Self-check (PR reviewed by myself and ready for feedback)

• Code compiles successfully

• Unit tests added

• All tests pass

• Comments added where necessary

• PR title and description updated

• Documentation Updated(or confirmed not needed)

• PR size is reasonable

r? @epage

I am not sure if it is worth keeping/asserting the output directory because, in these cases, we will not update the project itself. However, keeping it may help us prevent future changes that could affect them. Please let me know if you have a strong opinion on this.

View changes since this review

[Copilot]

Pull request overview

This PR fixes a bug in cargo info where it would incorrectly query the default registry instead of inspecting a local package when a default registry is configured but not explicitly specified.

Key Changes:

• Modified cargo info to prefer local packages when no explicit --registry or --index flag is provided
• Added detection for explicit registry/index arguments using args._contains()
• Added logic to override registry selection when a local package exists and no explicit registry is specified

Reviewed changes

Copilot reviewed 14 out of 32 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
src/bin/cargo/commands/info.rs	Added logic to detect explicit --registry or --index flags and pass this information to the info operation
src/cargo/ops/registry/info/mod.rs	Modified to accept explicit_registry parameter and prefer local packages when no explicit registry is specified
tests/testsuite/cargo_info/mod.rs	Registered two new test modules for the fix
tests/testsuite/cargo_info/with_default_registry_configured/*	Test case verifying local package is used when default registry is configured but not explicitly specified
tests/testsuite/cargo_info/with_default_registry_configured_and_specified/*	Test case verifying registry package is used when explicitly specified with --registry flag

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[0xPoe]

Thanks for your review! 💚 💙 💜 💛 ❤️