Update cargo submodule

[weihanglo]

5 commits in 101549dddbd2b08e806f50154e3aa4cb3374cc21..eb94155a9a60943bd7b1cb04abec42f5d0de6ddc
2026-04-08 12:51:20 +0000 to 2026-04-09 13:10:20 +0000

• Revert "GitHub fast path uses http_async" (Revert "GitHub fast path uses http_async" cargo#16861)
• Correct spelling in cargo info man page (Correct spelling in cargo info man page cargo#16863)
• chore: Update annotate-snippets to 0.12.15 (chore: Update annotate-snippets to 0.12.15 cargo#16859)
• fix(test): strip RUSTUP_TOOLCHAIN_SOURCE from test environment (fix(test): strip RUSTUP_TOOLCHAIN_SOURCE from test environment cargo#16857)
• Support target.'cfg(..)'.rustdocflags analogously to rustflags (Support target.'cfg(..)'.rustdocflags analogously to rustflags cargo#16846)

r? ghost

fixes #155048

[rustbot]

Some changes occurred in src/tools/cargo

cc @ehuss

[rustbot]

⚠️ Warning ⚠️

• Some commits in this PR modify submodules.

  If this was not intentional, see I changed a submodule on accident in the rustc dev guide.

[weihanglo]

Third cargo submodule update in a row this week 😅. There is a panic when installing from a GitHub repo cargo install --git <repo>, which is considered severe regression IMHO rust-lang/cargo#16860.

@bors r+ rollup=never p=1

[rust-bors]

📌 Commit 6b45278 has been approved by weihanglo

It is now in the queue for this repository.

[JonathanBrouwer]

@weihanglo Would it be acceptable to roll this PR up together with #154930?

[weihanglo]

@JonathanBrouwer looks harmless to me, sure.

[JonathanBrouwer]

@bors rollup=iffy