Update cargo submodule

[weihanglo]

View all comments

14 commits in fbb61be30e5f9ac3a6ad58e56a5c0f5db2d2b3ef..0b1123a48825309b697312b44fdb64b3df00c958
2026-05-26 15:08:03 +0000 to 2026-06-01 21:20:28 +0000

• chore(deps): update rust crate git2 to 0.21.0 (chore(deps): update rust crate git2 to 0.21.0 cargo#17060)
• chore(deps): update compatible (chore(deps): update compatible cargo#17057)
• fix(util): constant type for Redox OS (fix(util): constant type for Redox OS  cargo#17064)
• chore(deps): update crate-ci/typos action to v1.47.0 (chore(deps): update crate-ci/typos action to v1.47.0 cargo#17059)
• chore(deps): update embarkstudios/cargo-deny-action action to v2.0.20 (chore(deps): update embarkstudios/cargo-deny-action action to v2.0.20 cargo#17058)
• chore(deps): update cargo-semver-checks to v0.48.0 (chore(deps): update cargo-semver-checks to v0.48.0 cargo#17054)
• chore: bump to 0.99.0; update changelog (chore: bump to 0.99.0; update changelog cargo#17049)
• Bump cargo-util-schemas to 0.14.2 (Bump cargo-util-schemas to 0.14.2 cargo#17048)
• feat: Add edition for scripts anytime we mutate the manifest (feat: Add edition for scripts anytime we mutate the manifest cargo#17038)
• docs: clarify on crate removal post RFC 3660 (docs: clarify on crate removal post RFC 3660 cargo#17036)
• feat: Add --output-format=json to cargo doc as an unstable option (feat: Add --output-format=json to cargo doc as an unstable option cargo#17025)
• feat(diag): Add the 'cargo::default' group (feat(diag): Add the 'cargo::default' group cargo#17033)
• fix(add): Ensure erros are lower case (fix(add): Ensure erros are lower case cargo#17037)
• fix(diag): Report summaries for unused_deps (fix(diag): Report summaries for unused_deps cargo#17034)

[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 723ebc9 has been approved by weihanglo

It is now in the queue for this repository.

🌲 The tree is currently closed for pull requests below priority 5. This pull request will be tested once the tree is reopened.

[jhpratt]

Let's see how things are going a few hours later

@bors p=6

[rust-bors]

💔 Test for 55901aa failed: CI. Failed job:

• auto - dist-various-1 (web logs, enhanced plaintext logs)

[jhpratt]

@bors p=1 retry

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[JonathanBrouwer]

@bors p=6

[JonathanBrouwer]

@bors retry

[rust-bors]

💔 Test for 206251b failed: CI. Failed job:

• auto - dist-android (web logs, enhanced plaintext logs)

[JonathanBrouwer]

@bors retry
@bors treeclosed=5

[rust-bors]

Tree closed for PRs with priority less than 5.

[rust-log-analyzer]

A job failed! Check out the build log: (web) (plain enhanced) (plain)

Click to see the possible cause of the failure (guessed by this bot)

[rust-bors]

☀️ Test successful - CI
Approved by: weihanglo
Duration: 3h 34m 18s
Pushing 042c759 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 53509ca (parent) -> 042c759 (this PR)

Test differences

Show 15 test diffs

Stage 2

• build_dir::cargo_doc_json_should_output_to_target_dir: [missing] -> ignore (--output-format is unstable) (J0)
• build_dir_legacy::cargo_doc_json_should_output_to_target_dir: [missing] -> ignore (--output-format is unstable) (J0)
• diagnostics::lint::tests::default_after_primary: [missing] -> pass (J0)
• diagnostics::lint::tests::default_before_primary: [missing] -> pass (J0)
• diagnostics::lint::tests::default_group_overrides_default: [missing] -> pass (J0)
• diagnostics::lint::tests::default_higher_than_primary: [missing] -> pass (J0)
• diagnostics::lint::tests::default_lower_than_primary: [missing] -> pass (J0)
• doc::doc_invalid_output_format: [missing] -> pass (J0)
• doc::doc_output_format_html_stable: [missing] -> pass (J0)
• doc::doc_output_format_json_no_deps: [missing] -> ignore (--output-format is unstable) (J0)
• doc::doc_output_format_json_with_deps: [missing] -> ignore (--output-format is unstable) (J0)
• doc::doc_output_format_json_without_unstable_options: [missing] -> pass (J0)
• lints::unused_dependencies::deny_in_manifest: [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 042c759f774872cf2f94c6685ce87e24c046c722 --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-apple: 1h 26m -> 2h 10m (+50.5%)
2. x86_64-gnu-gcc-core-tests: 14m 4s -> 8m 11s (-41.8%)
3. dist-x86_64-apple: 1h 35m -> 2h 13m (+39.5%)
4. dist-aarch64-linux: 1h 49m -> 2h 31m (+38.8%)
5. x86_64-msvc-ext1: 1h 40m -> 2h 17m (+36.1%)
6. x86_64-gnu-llvm-22-2: 1h 39m -> 1h 13m (-25.8%)
7. dist-powerpc64le-linux-musl: 1h 18m -> 1h 37m (+25.0%)
8. dist-armv7-linux: 1h 41m -> 1h 16m (-24.5%)
9. x86_64-msvc-2: 2h 29m -> 1h 56m (-21.9%)
10. x86_64-gnu-aux: 1h 49m -> 2h 11m (+19.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 (042c759): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

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

Max RSS (memory usage)

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

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: 509.672s -> 516.236s (1.29%)
Artifact size: 400.72 MiB -> 400.65 MiB (-0.02%)