Update cargo submodule

[weihanglo]

13 commits in e91b2baa632c0c7e84216c91ecfe107c37d887c1..3861f60f6b58f57524c0e7aab1f5c1ad83e35409
2025-12-13 16:29:21 +0000 to 2025-12-19 21:53:33 +0000

• fix(sbom): Don't set CARGO_SBOM_PATH when empty (like stable) (fix(sbom): Don't set CARGO_SBOM_PATH when empty (like stable)  cargo#16419)
• chore(ci): report-timings to upload HTML report (chore(ci): report-timings to upload HTML report cargo#16416)
• fix(report): get the same feature parity of --timings (fix(report): get the same feature parity of --timings cargo#16414)
• fix(docs): Document the only possible values for DEBUG in build scripts (fix(docs): Document the only possible values for DEBUG in build scripts cargo#16413)
• fix(log): emit fingeprint log also for no-rebuild unit (fix(log): emit fingeprint log also for no-rebuild unit cargo#16408)
• Fix link to doc_cfg docs in cargo book (Fix link to doc_cfg docs in cargo book cargo#16404)
• Add best pratice for how to check in generated files (Add best pratice for how to check in generated files cargo#16405)
• test: Use a larger default term width (test: Use a larger default term width cargo#16403)
• Document more services and permissions of the cargo team (Document more services and permissions of the cargo team cargo#16402)
• fix(new): Improve quality of package name error messages (fix(new): Improve quality of package name error messages cargo#16398)
• feat(log): add more log events (feat(log): add more log events cargo#16390)
• chore: bump to 0.95.0; update changelog (chore: bump to 0.95.0; update changelog cargo#16395)
• Cache submodule into git db (Cache submodule into git db cargo#16246)

r? ghost

[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

[bors]

📌 Commit 3e5b12e has been approved by weihanglo

It is now in the queue for this repository.

[bors]

⌛ Testing commit 3e5b12e with merge d0835ad...

[bors]

☀️ Test successful - checks-actions
Approved by: weihanglo
Pushing d0835ad 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 838a912 (parent) -> d0835ad (this PR)

Test differences

Show 4 test diffs

Stage 2

• build_analysis::log_msg_resolution_events: [missing] -> pass (J0)
• build_analysis::log_msg_unit_graph: [missing] -> pass (J0)
• cargo_report_timings::html_snapshot::case: pass -> [missing] (J0)
• git::dep_with_cached_submodule: [missing] -> pass (J0)

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 d0835adc4e114eac911150b3692b830b5583223a --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. dist-aarch64-linux: 8743.3s -> 6390.0s (-26.9%)
2. x86_64-rust-for-linux: 3127.6s -> 2504.8s (-19.9%)
3. i686-gnu-nopt-1: 8173.4s -> 6855.3s (-16.1%)
4. pr-check-1: 1996.8s -> 1692.8s (-15.2%)
5. x86_64-gnu-tools: 3744.4s -> 3263.7s (-12.8%)
6. aarch64-gnu-llvm-20-1: 3820.4s -> 3359.1s (-12.1%)
7. aarch64-apple: 9742.2s -> 8576.4s (-12.0%)
8. dist-aarch64-msvc: 5561.9s -> 6225.3s (+11.9%)
9. x86_64-gnu-gcc: 3433.2s -> 3031.7s (-11.7%)
10. i686-gnu-2: 6042.6s -> 5357.4s (-11.3%)

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 (d0835ad): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results (secondary 0.9%)

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.9%	[0.8%, 0.9%]	2
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-	-	0

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 479.839s -> 478.448s (-0.29%)
Artifact size: 390.55 MiB -> 390.61 MiB (0.02%)