Update cargo submodule

[weihanglo]

9 commits in 598ab48ec328e3e4f5e4e373d8df7264bc8e27cd..a595d0da21f228b7fdae64d3d5c0e527ea66bb59
2026-06-17 02:39:50 +0000 to 2026-06-20 13:42:59 +0000

• fix(host-config): dont apply target config to host artifacts (fix(host-config): dont apply target config to host artifacts  cargo#17123)
• chore(deps): update msrv to v1.94 (chore(deps): update msrv to v1.94 cargo#17121)
• test(update): show cross-registry multi-spec precise (test(update): show cross-registry multi-spec precise cargo#17119)
• fix(resolver): hint how to resolve too-new versions (fix(resolver): hint how to resolve too-new versions cargo#17118)
• fix(add): list too-new versions and how to override (fix(add): list too-new versions and how to override cargo#17117)
• feat: -Zmin-publish-age (RFC 3923) (feat: -Zmin-publish-age (RFC 3923) cargo#17012)
• feat(diag): Support build.warnings for cargo lints (feat(diag): Support build.warnings for cargo lints cargo#17112)
• Remove windows-sys dependencies older than 0.61 (Remove windows-sys dependencies older than 0.61 cargo#17115)
• fix(install): Run cargo lints like rustc lints (fix(install): Run cargo lints like rustc lints cargo#17107)

[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 89a0674 has been approved by weihanglo

It is now in the queue for this repository.

[rust-bors]

💔 Test for 8ef73c0 failed: CI. Failed job:

• auto - x86_64-gnu-stable (web logs, enhanced plaintext logs)

[weihanglo]

Caused by:
  failed to load source for dependency `askama_derive`

Caused by:
  unable to update registry `crates-io`

Caused by:
  download of as/ka/askama_derive failed

Caused by:
  curl failed

GitHub is f'd again 😞

Anyway, we need to wait for rust-lang/cargo#17123.

@bors r-

[rust-bors]

View changes since this unapproval

[weihanglo]

@bors r+

[rust-bors]

📌 Commit cd4e6f4 has been approved by weihanglo

It is now in the queue for this repository.

[rust-bors]

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 11m 12s
Pushing fffed27 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 4008bbd (parent) -> fffed27 (this PR)

Test differences

Show 62 test diffs

Stage 2

• build_script::target_linker_does_not_apply_to_build_script_with_host_config: [missing] -> pass (J0)
• build_script::target_runner_does_not_apply_to_build_script_with_host_config: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_alt_registry_falls_through_to_global: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_at_threshold_boundary_is_acceptable: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_crates_io_scope_excludes_alt_registry: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_future_pubtime_is_too_new: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_just_inside_threshold_is_too_new: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_missing_pubtime_is_acceptable: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_no_applicable_scope_is_acceptable: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_older_than_threshold_is_acceptable: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_out_of_range_threshold_is_too_new: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_per_registry_overrides_global: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_per_registry_too_new: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_per_registry_zero_overrides_global: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_reports_exact_age: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_zero_disables_threshold: [missing] -> pass (J0)
• core::resolver::version_prefs::test::publish_age_zero_stops_scope_fallthrough: [missing] -> pass (J0)
• core::resolver::version_prefs::test::rounds_to_a_single_unit: [missing] -> pass (J0)
• install::cap_lints_path: [missing] -> pass (J0)
• install::cap_lints_registry: [missing] -> pass (J0)
• min_publish_age::cargo_add_all_versions_too_new: [missing] -> pass (J0)
• min_publish_age::cargo_add_skips_too_new: [missing] -> pass (J0)
• min_publish_age::cargo_install_allows_too_new_deps: [missing] -> pass (J0)
• min_publish_age::cargo_install_ignores_min_publish_age: [missing] -> pass (J0)
• min_publish_age::cargo_install_locked_allows_too_new_dep: [missing] -> pass (J0)
• min_publish_age::cargo_install_path_allows_too_new_deps: [missing] -> pass (J0)
• min_publish_age::feature_gated: [missing] -> pass (J0)
• min_publish_age::feature_gated_env: [missing] -> pass (J0)
• min_publish_age::filters_too_new_versions: [missing] -> pass (J0)
• min_publish_age::incompatible_publish_age_allow: [missing] -> pass (J0)
• min_publish_age::incompatible_publish_age_deny: [missing] -> pass (J0)
• min_publish_age::locked_versions_preserved: [missing] -> pass (J0)
• min_publish_age::no_candidates_error: [missing] -> pass (J0)
• min_publish_age::patched_versions_preserved: [missing] -> pass (J0)
• min_publish_age::publish_age_invalid: [missing] -> pass (J0)
• min_publish_age::publish_age_zero: [missing] -> pass (J0)
• min_publish_age::registries_alt: [missing] -> pass (J0)
• min_publish_age::registries_alt_ignores_registry_default: [missing] -> pass (J0)
• min_publish_age::registries_alt_overrides_global: [missing] -> pass (J0)
• min_publish_age::registries_alt_respects_global: [missing] -> pass (J0)
• min_publish_age::registries_crates_io: [missing] -> pass (J0)
• min_publish_age::registries_crates_io_overrides_registry_default: [missing] -> pass (J0)
• min_publish_age::registry_alt_ignores_min_publish_age: [missing] -> pass (J0)
• min_publish_age::registry_default: [missing] -> pass (J0)
• min_publish_age::registry_default_overrides_global: [missing] -> pass (J0)
• min_publish_age::registry_default_zero_overrides_global: [missing] -> pass (J0)
• min_publish_age::report_rust_version_note_over_too_new_note: [missing] -> pass (J0)
• min_publish_age::report_unchanged_too_new_version: [missing] -> pass (J0)
• min_publish_age::resolve_with_backtracking: [missing] -> pass (J0)
• min_publish_age::update_precise_to_too_new: [missing] -> pass (J0)
• min_publish_age::update_precise_with_allow: [missing] -> pass (J0)
• min_publish_age::versions_without_pubtime_unaffected: [missing] -> pass (J0)
• min_publish_age::warns_on_resolver_config_without_flag: [missing] -> pass (J0)
• update::precise_with_multiple_specs_cross_registry: [missing] -> pass (J0)
• util::time_span::tests::time_span_errors: [missing] -> pass (J0)
• util::time_span::tests::time_spans: [missing] -> pass (J0)
• warning_override::lint_build_result_pass: [missing] -> pass (J0)
• warning_override::lint_parse_pass: [missing] -> pass (J0)

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

Job group index

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

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard fffed276b51cf514622e8d3109d620501cc01670 --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-x86_64-freebsd: 56m 47s -> 1h 32m (+63.5%)
2. x86_64-gnu-gcc-core-tests: 5m 46s -> 8m 11s (+41.7%)
3. dist-aarch64-apple: 2h 6m -> 1h 26m (-31.7%)
4. x86_64-rust-for-linux: 34m 28s -> 45m 7s (+30.9%)
5. x86_64-msvc-1: 2h 38m -> 1h 57m (-25.6%)
6. dist-x86_64-msvc: 1h 35m -> 1h 58m (+24.6%)
7. i686-gnu-nopt-1: 2h 6m -> 1h 36m (-23.9%)
8. x86_64-gnu-nopt: 1h 53m -> 2h 19m (+22.5%)
9. i686-msvc-2: 1h 58m -> 1h 33m (-21.8%)
10. x86_64-gnu-llvm-22-2: 1h 37m -> 1h 16m (-21.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 (fffed27): 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.2%	[-0.3%, -0.2%]	2
All ❌✅ (primary)	-	-	0

Max RSS (memory usage)

Results (primary 2.9%, secondary -3.1%)

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

	mean	range	count
Regressions ❌ (primary)	2.9%	[1.6%, 4.2%]	2
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-3.1%	[-3.1%, -3.1%]	1
All ❌✅ (primary)	2.9%	[1.6%, 4.2%]	2

Cycles

This perf run didn't have relevant results for this metric.

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 487.822s -> 481.959s (-1.20%)
Artifact size: 391.12 MiB -> 390.78 MiB (-0.09%)