Update cargo submodule

[weihanglo]

13 commits in 4d1f984518c77fad6eeef4f40153b002a659e662..fbb61be30e5f9ac3a6ad58e56a5c0f5db2d2b3ef
2026-05-15 17:12:01 +0000 to 2026-05-26 15:08:03 +0000

• fix(compiler): forward verbose flag to rustc for local crates (fix(compiler): forward verbose flag to rustc for local crates cargo#17006)
• Fix CVE-2026-5222 and CVE-2026-5223 (Fix CVE-2026-5222 and CVE-2026-5223 cargo#17031)
• Don't use the network for a publish dry-run test ( Don't use the network for a publish dry-run test  cargo#17027)
• feat: Break out RegistryConfig and crate_url for interpreting RegistryConfig::dl (feat: Break out RegistryConfig and crate_url for interpreting RegistryConfig::dl cargo#17011)
• refactor(diag): Sort the PARSE_PASS_RULES (refactor(diag): Sort the PARSE_PASS_RULES cargo#17019)
• fix(artifact)!: Remove compat mode from artifacts (fix(artifact)!: Remove compat mode from artifacts cargo#17016)
• refactor(diag): Simplify adding of new diagnostics (refactor(diag): Simplify adding of new diagnostics cargo#17015)
• test(package): Mark a network test that timed out on me (test(package): Mark a network test that timed out on me cargo#17017)
• refactor(diag): Pull in the parse pass (refactor(diag): Pull in the parse pass cargo#17008)
• test(lints): Avoid compiling where possible (test(lints): Avoid compiling where possible cargo#17007)
• fix(diag): Report deferred diagnostics like other diagnostics (fix(diag): Report deferred diagnostics like other diagnostics cargo#16994)
• refactor: drop -Zunstable-options for rustdoc --emit (refactor: drop -Zunstable-options for rustdoc --emit cargo#17002)
• chore(deps): update msrv (1 version) to v1.95 (chore(deps): update msrv (1 version) to v1.95 cargo#17001)

[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]

@bors r+ rollup=never p=1

[rust-bors]

📌 Commit 2292996 has been approved by weihanglo

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 10m 5s
Pushing 2cfb951 to main...

[github-actions]

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing d1fc603 (parent) -> 2cfb951 (this PR)

Test differences

Show 8 test diffs

Stage 2

• diagnostics::rules::tests::ensure_parse_passed_in_lints: [missing] -> pass (J0)
• diagnostics::rules::tests::ensure_sorted_parse_pass_rules: [missing] -> pass (J0)
• registry::package_lock_as_a_symlink_inside_package_is_invalid: [missing] -> pass (J0)
• registry::package_lock_as_a_symlink_inside_package_is_overwritten: pass -> [missing] (J0)
• rustc::verbose_flag_forwarded_to_rustc_for_local_only: [missing] -> pass (J0)
• sources::git::source::test::test_canonicalize_idents_does_not_strip_dot_git_for_sparse: [missing] -> pass (J0)

Additionally, 2 doctest diffs were found. These are ignored, as they are noisy.

Job group index

• J0: aarch64-apple, aarch64-gnu, x86_64-gnu-aux, x86_64-msvc-ext1

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 2cfb951a24de2520de67f6911fd1fc0045a2662e --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

1. x86_64-gnu-gcc-core-tests: 7m 42s -> 14m 32s (+88.4%)
2. dist-apple-various: 1h 39m -> 2h 32m (+53.3%)
3. x86_64-gnu-debug: 1h 30m -> 2h 12m (+46.6%)
4. x86_64-msvc-ext1: 1h 45m -> 2h 19m (+32.3%)
5. pr-check-1: 26m 57s -> 34m 24s (+27.7%)
6. dist-powerpc64le-linux-gnu: 1h 18m -> 1h 39m (+27.6%)
7. dist-x86_64-msvc-alt: 2h 50m -> 2h 6m (-25.6%)
8. test-various: 1h 56m -> 2h 19m (+20.0%)
9. dist-i686-mingw: 2h 13m -> 2h 39m (+19.6%)
10. x86_64-rust-for-linux: 44m 56s -> 53m 26s (+18.9%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

[rust-timer]

Finished benchmarking commit (2cfb951): comparison URL.

Overall result: ✅ improvements - no action needed

@rustbot label: -perf-regression

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-0.3%	[-0.4%, -0.3%]	3
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary -2.3%, secondary 2.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	2.1%	[2.1%, 2.1%]	1
Improvements ✅ (primary)	-2.3%	[-2.3%, -2.3%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-2.3%	[-2.3%, -2.3%]	1

Cycles

Results (primary 0.6%, secondary -0.6%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	2.0%	[1.5%, 2.6%]	2
Regressions ❌ (secondary)	3.7%	[3.7%, 3.7%]	1
Improvements ✅ (primary)	-2.3%	[-2.3%, -2.3%]	1
Improvements ✅ (secondary)	-2.8%	[-2.9%, -2.7%]	2
All ❌✅ (primary)	0.6%	[-2.3%, 2.6%]	3

Binary size

Results (secondary 0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	0.0%	[0.0%, 0.0%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Bootstrap: 510.439s -> 510.57s (0.03%)
Artifact size: 400.53 MiB -> 400.65 MiB (0.03%)