Weekly `cargo update`
Automation to keep dependencies in Cargo.lock current.
r? dep-bumps
The following is the output from cargo update:
compiler & tools dependencies:
Locking 49 packages to latest compatible versions
Updating addr2line v0.24.2 -> v0.25.1
Updating anstyle-svg v0.1.11 -> v0.1.12
Updating backtrace v0.3.75 -> v0.3.76
Updating clap v4.5.51 -> v4.5.53
Updating clap_builder v4.5.51 -> v4.5.53
Adding console v0.16.1
Updating cxx v1.0.188 -> v1.0.190
Updating cxx-build v1.0.188 -> v1.0.190
Updating cxxbridge-cmd v1.0.188 -> v1.0.190
Updating cxxbridge-flags v1.0.188 -> v1.0.190
Updating cxxbridge-macro v1.0.188 -> v1.0.190
Updating flate2 v1.1.5 -> v1.1.7
Updating git2 v0.20.2 -> v0.20.3
Updating hashbrown v0.16.0 -> v0.16.1
Updating indexmap v2.12.0 -> v2.12.1
Adding indicatif v0.18.3
Updating js-sys v0.3.82 -> v0.3.83
Updating libc v0.2.177 -> v0.2.178
Updating libgit2-sys v0.18.2+1.9.1 -> v0.18.3+1.9.2
Updating log v0.4.28 -> v0.4.29
Updating mio v1.1.0 -> v1.1.1
Updating pest v2.8.3 -> v2.8.4
Updating pest_derive v2.8.3 -> v2.8.4
Updating pest_generator v2.8.3 -> v2.8.4
Updating pest_meta v2.8.3 -> v2.8.4
Updating syn v2.0.110 -> v2.0.111
Updating tracing v0.1.41 -> v0.1.43
Updating tracing-attributes v0.1.30 -> v0.1.31
Updating tracing-core v0.1.34 -> v0.1.35
Updating tracing-subscriber v0.3.20 -> v0.3.22
Updating ui_test v0.30.3 -> v0.30.4
Updating unicode-ident v1.0.18 -> v1.0.22
Updating unicode-normalization v0.1.24 -> v0.1.25
Updating unicode-properties v0.1.3 -> v0.1.4
Updating unicode-script v0.5.7 -> v0.5.8
Adding unit-prefix v0.5.2
Updating utf8-width v0.1.7 -> v0.1.8
Updating uuid v1.18.1 -> v1.19.0
Updating wasm-bindgen v0.2.105 -> v0.2.106
Updating wasm-bindgen-macro v0.2.105 -> v0.2.106
Updating wasm-bindgen-macro-support v0.2.105 -> v0.2.106
Updating wasm-bindgen-shared v0.2.105 -> v0.2.106
Adding wasm-encoder v0.243.0
Adding wasmparser v0.243.0
Updating wast v241.0.2 -> v243.0.0
Updating wat v1.241.2 -> v1.243.0
Updating winnow v0.7.13 -> v0.7.14
Updating zerocopy v0.8.27 -> v0.8.31
Updating zerocopy-derive v0.8.27 -> v0.8.31
note: pass `--verbose` to see 39 unchanged dependencies behind latest
library dependencies:
Locking 3 packages to latest compatible versions
Updating dlmalloc v0.2.11 -> v0.2.12
Updating libc v0.2.177 -> v0.2.178
Updating windows-sys v0.60.2 -> v0.61.2
Removing windows-targets v0.53.5
Removing windows_aarch64_gnullvm v0.53.1
Removing windows_aarch64_msvc v0.53.1
Removing windows_i686_gnu v0.53.1
Removing windows_i686_gnullvm v0.53.1
Removing windows_i686_msvc v0.53.1
Removing windows_x86_64_gnu v0.53.1
Removing windows_x86_64_gnullvm v0.53.1
Removing windows_x86_64_msvc v0.53.1
note: pass `--verbose` to see 5 unchanged dependencies behind latest
rustbook dependencies:
Locking 29 packages to latest compatible versions
Updating anstyle-query v1.1.4 -> v1.1.5
Updating anstyle-wincon v3.0.10 -> v3.0.11
Updating cc v1.2.45 -> v1.2.49
Updating clap v4.5.51 -> v4.5.53
Updating clap_builder v4.5.51 -> v4.5.53
Updating clap_complete v4.5.60 -> v4.5.61
Updating crypto-common v0.1.6 -> v0.1.7
Updating find-msvc-tools v0.1.4 -> v0.1.5
Updating flate2 v1.1.5 -> v1.1.7
Downgrading generic-array v0.14.9 -> v0.14.7 (available: v0.14.9)
Updating hashbrown v0.16.0 -> v0.16.1
Updating indexmap v2.12.0 -> v2.12.1
Updating js-sys v0.3.82 -> v0.3.83
Updating libc v0.2.177 -> v0.2.178
Updating log v0.4.28 -> v0.4.29
Updating pest v2.8.3 -> v2.8.4
Updating pest_derive v2.8.3 -> v2.8.4
Updating pest_generator v2.8.3 -> v2.8.4
Updating pest_meta v2.8.3 -> v2.8.4
Removing phf v0.13.1
Downgrading phf_codegen v0.13.1 -> v0.11.3
Removing phf_generator v0.13.1
Removing phf_shared v0.13.1
Downgrading string_cache v0.9.0 -> v0.8.9
Downgrading string_cache_codegen v0.6.1 -> v0.5.4
Updating syn v2.0.110 -> v2.0.111
Updating wasm-bindgen v0.2.105 -> v0.2.106
Updating wasm-bindgen-macro v0.2.105 -> v0.2.106
Updating wasm-bindgen-macro-support v0.2.105 -> v0.2.106
Updating wasm-bindgen-shared v0.2.105 -> v0.2.106
Downgrading web_atoms v0.1.4 -> v0.1.3
Updating winnow v0.7.13 -> v0.7.14
note: pass `--verbose` to see 2 unchanged dependencies behind latest
These commits modify the Cargo.lock file. Unintentional changes to Cargo.lock can be introduced when switching branches and rebasing PRs.
If this was unintentional then you should revert the changes before this PR is merged. Otherwise, you can ignore this comment.
These commits modify the library/Cargo.lock file. Unintentional changes to library/Cargo.lock can be introduced when switching branches and rebasing PRs.
If this was unintentional then you should revert the changes before this PR is merged. Otherwise, you can ignore this comment.
@bors r+ rollup=iffy
:pushpin: Commit 0da85854281eb858fb8f6526c1242da47d8986cf has been approved by clubby789
It is now in the queue for this repository.
Failed in rollup: https://github.com/rust-lang/rust/pull/145552#issuecomment-3196169313
@bors r- @rustbot blocked (needs #145478)
I've managed to thoroughly confuse myself with these cargo-related PRs. I'll try to un-confuse myself with a try job:
@bors try jobs=dist-loongarch64-musl
:hourglass: Trying commit 0da85854281eb858fb8f6526c1242da47d8986cf with merge a830c63185352e6d19e67d948ad98e866634d345…
To cancel the try build, run the command @bors try cancel.
https://github.com/rust-lang/libc/compare/0.2.174...0.2.175#diff-6d0c7e87f8f6c82de4bb365536c23026b994addd4ecb97ca9faad96059d2ef04
I see some Musl/statx related diffs in the libc bump, which could transitively cause issues with glob imports
https://github.com/bytecodealliance/rustix/issues/1496
The job dist-loongarch64-musl failed! Check out the build log: (web) (plain enhanced) (plain)
Click to see the possible cause of the failure (guessed by this bot)
error[E0659]: `STATX_NLINK` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:79:26
|
79 | const NLINK = c::STATX_NLINK;
| ^^^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_NLINK` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
---
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_NLINK` to disambiguate
error[E0659]: `STATX_UID` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:82:24
|
82 | const UID = c::STATX_UID;
| ^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_UID` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
---
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_UID` to disambiguate
error[E0659]: `STATX_GID` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:85:24
|
85 | const GID = c::STATX_GID;
| ^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_GID` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
---
error[E0659]: `STATX_ATIME` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:88:26
|
88 | const ATIME = c::STATX_ATIME;
| ^^^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_ATIME` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
---
error[E0659]: `STATX_MTIME` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:91:26
|
91 | const MTIME = c::STATX_MTIME;
| ^^^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_MTIME` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
---
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_CTIME` to disambiguate
error[E0659]: `STATX_INO` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:97:24
|
97 | const INO = c::STATX_INO;
| ^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_INO` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
---
error[E0659]: `STATX_BTIME` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:109:26
|
109 | const BTIME = c::STATX_BTIME;
| ^^^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_BTIME` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
---
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_BTIME` to disambiguate
error[E0659]: `STATX_MNT_ID` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:112:27
|
112 | const MNT_ID = c::STATX_MNT_ID;
| ^^^^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_MNT_ID` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
---
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_MNT_ID` to disambiguate
error[E0659]: `STATX_DIOALIGN` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:115:29
|
115 | const DIOALIGN = c::STATX_DIOALIGN;
| ^^^^^^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_DIOALIGN` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
7 | pub(crate) use libc::*;
| ^^^^^^^
= help: consider adding an explicit import of `STATX_DIOALIGN` to disambiguate
note: `STATX_DIOALIGN` could also refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:512:16
|
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_DIOALIGN` to disambiguate
error[E0659]: `STATX_ALL` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:118:24
|
118 | const ALL = c::STATX_ALL;
---
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_ATTR_APPEND` to disambiguate
error[E0659]: `STATX_ATTR_NODUMP` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:140:27
|
140 | const NODUMP = c::STATX_ATTR_NODUMP as u64;
| ^^^^^^^^^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_ATTR_NODUMP` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
7 | pub(crate) use libc::*;
| ^^^^^^^
= help: consider adding an explicit import of `STATX_ATTR_NODUMP` to disambiguate
note: `STATX_ATTR_NODUMP` could also refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:512:16
|
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_ATTR_NODUMP` to disambiguate
error[E0659]: `STATX_ATTR_ENCRYPTED` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:143:30
|
143 | const ENCRYPTED = c::STATX_ATTR_ENCRYPTED as u64;
---
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_ATTR_VERITY` to disambiguate
error[E0659]: `STATX_ATTR_DAX` is ambiguous
--> /rust/deps/rustix-1.0.8/src/fs/statx.rs:155:24
|
155 | const DAX = c::STATX_ATTR_DAX as u64;
| ^^^^^^^^^^^^^^ ambiguous name
|
= note: ambiguous because of multiple glob imports of a name in the same module
note: `STATX_ATTR_DAX` could refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:7:16
|
7 | pub(crate) use libc::*;
| ^^^^^^^
= help: consider adding an explicit import of `STATX_ATTR_DAX` to disambiguate
note: `STATX_ATTR_DAX` could also refer to the constant imported here
--> /rust/deps/rustix-1.0.8/src/backend/libc/c.rs:512:16
|
512 | pub(crate) use statx_flags::*;
| ^^^^^^^^^^^^^^
= help: consider adding an explicit import of `STATX_ATTR_DAX` to disambiguate
[RUSTC-TIMING] tracing_attributes test:false 2.589
Compiling tracing v0.1.37
[RUSTC-TIMING] proc_macro_hack test:false 1.078
[RUSTC-TIMING] unic_langid_impl test:false 0.491
:broken_heart: Test for a830c63185352e6d19e67d948ad98e866634d345 failed: CI. Failed jobs:
-
try - dist-loongarch64-musl(web logs, extended logs)
Fixing in #145567, this PR can be left to auto-update in a few days
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
The job aarch64-gnu-llvm-19-2 failed! Check out the build log: (web) (plain enhanced) (plain)
Click to see the possible cause of the failure (guessed by this bot)
[TIMING:end] tool::Tidy { compiler: Compiler { stage: 0, host: aarch64-unknown-linux-gnu, forced_compiler: false }, target: aarch64-unknown-linux-gnu } -- 0.000
fmt check
fmt: checked 6337 files
tidy check
tidy error: could not find allowed package `semver`
Remove from PERMITTED_DEPENDENCIES list if it is no longer used.
Go to `src/tools/tidy/src/deps.rs:229` for the list.
Go to `src/tools/tidy/src/deps.rs:229` for the list.
tidy error: Dependency for library not explicitly permitted: registry+https://github.com/rust-lang/crates.io-index#[email protected]
Checking tidy rustdoc_json...
No error code explanation was removed!
tidy: Skipping binary file check, read-only filesystem
some tidy checks failed
Command `/checkout/obj/build/aarch64-unknown-linux-gnu/stage1-tools-bin/rust-tidy /checkout /checkout/obj/build/aarch64-unknown-linux-gnu/stage0/bin/cargo /checkout/obj/build 4 npm` failed with exit code 1
Created at: src/bootstrap/src/core/build_steps/tool.rs:1583:23
Executed at: src/bootstrap/src/core/build_steps/test.rs:1225:29
Command has failed. Rerun with -v to see more details.
Bootstrap failed while executing `--stage 2 test --skip tests --skip coverage-map --skip coverage-run --skip library --skip tidyselftest`
Build completed unsuccessfully in 0:00:59
local time: Mon Aug 25 13:59:00 UTC 2025
network time: Mon, 25 Aug 2025 13:59:00 GMT
##[error]Process completed with exit code 1.
:umbrella: The latest upstream changes (presumably #145871) made this pull request unmergeable. Please resolve the merge conflicts.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
:umbrella: The latest upstream changes (presumably #146160) made this pull request unmergeable. Please resolve the merge conflicts.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
:umbrella: The latest upstream changes (presumably #146700) made this pull request unmergeable. Please resolve the merge conflicts.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
:umbrella: The latest upstream changes (presumably #147405) made this pull request unmergeable. Please resolve the merge conflicts.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
:umbrella: The latest upstream changes (presumably #148100) made this pull request unmergeable. Please resolve the merge conflicts.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
:umbrella: The latest upstream changes (presumably #148356) made this pull request unmergeable. Please resolve the merge conflicts.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed.
Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers.