Skip to content

Bump the cargo group across 6 directories with 9 updates - #2

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/cargo/src/tools/rustfmt/cargo-f1a3f38cc9
Closed

Bump the cargo group across 6 directories with 9 updates#2
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/cargo/src/tools/rustfmt/cargo-f1a3f38cc9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Mar 4, 2026

Copy link
Copy Markdown

Bumps the cargo group with 1 update in the /src/tools/rustfmt directory: tracing-subscriber.
Bumps the cargo group with 2 updates in the /src/tools/rustbook directory: ammonia and time.
Bumps the cargo group with 3 updates in the /src/tools/rust-analyzer directory: tracing-subscriber, time and crossbeam-channel.
Bumps the cargo group with 2 updates in the /src/tools/miri directory: tracing-subscriber and crossbeam-channel.
Bumps the cargo group with 1 update in the /compiler/rustc_codegen_gcc directory: rustix.
Bumps the cargo group with 7 updates in the / directory:

Package From To
ammonia 4.0.0 4.0.1
time 0.3.36 0.3.47
crossbeam-channel 0.5.13 0.5.15
tokio 1.38.0 1.38.2
bytes 1.6.0 1.11.1
zerovec 0.10.2 0.10.4
zerovec-derive 0.10.2 0.10.3

Updates tracing-subscriber from 0.3.17 to 0.3.20

Release notes

Sourced from tracing-subscriber's releases.

tracing-subscriber 0.3.20

Security Fix: ANSI Escape Sequence Injection (CVE-TBD)

Impact

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

Solution

Version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.

Affected Versions

All versions of tracing-subscriber prior to 0.3.20 are affected by this vulnerability.

Recommendations

Immediate Action Required: We recommend upgrading to tracing-subscriber 0.3.20 immediately, especially if your application:

  • Logs user-provided input (form data, HTTP headers, query parameters, etc.)
  • Runs in environments where terminal output is displayed to users

Migration

This is a patch release with no breaking API changes. Simply update your Cargo.toml:

[dependencies]
tracing-subscriber = "0.3.20"

Acknowledgments

We would like to thank zefr0x who responsibly reported the issue at security@tokio.rs.

If you believe you have found a security vulnerability in any tokio-rs project, please email us at security@tokio.rs.

tracing-subscriber 0.3.19

[ [crates.io][crate-0.3.19] ] | [ [docs.rs][docs-0.3.19] ]

This release updates the tracing dependency to [v0.1.41][tracing-0.1.41] and the tracing-serde dependency to [v0.2.0][tracing-serde-0.2.0].

Added

... (truncated)

Commits

Updates ammonia from 4.0.0 to 4.1.2

Release notes

Sourced from ammonia's releases.

4.1.2

  • fix: unexpected namespace switches after cleanup can cause mXSS (reported by zzm0902@shu.edu.cn)

4.1.1

4.1.0

  • chore: bump MSRV to 1.80.0
  • chore: switch to std's LazyLock instead of once_cell's Lazy
  • feature: improve panic message when clean_content_tags conflicts with other options
  • feature: add support for sanitizing the style attribute

4.0.1

  • fix: unexpected namespace switches after cleanup can cause mXSS (reported by zzm0902@shu.edu.cn, backport 4.1.2)
Changelog

Sourced from ammonia's changelog.

4.1.2

  • fix: unexpected namespace switches after cleanup can cause mXSS (reported by zzm0902@shu.edu.cn)

4.1.1

4.1.0

  • chore: bump MSRV to 1.80.0
  • chore: switch to std's LazyLock instead of once_cell's Lazy
  • feature: improve panic message when clean_content_tags conflicts with other options
  • feature: add support for sanitizing the style attribute

4.0.1

  • fix: unexpected namespace switches after cleanup can cause mXSS (backport 4.1.2)
Commits
  • de02971 Release 4.1.2 with security fix
  • 7e9754b Merge pull request #218 from atouchet/trav
  • f1e732c Delete .travis.yml
  • 5d54a86 Merge pull request #216 from atouchet/urls
  • 52a7d97 Update Readme
  • a14a5eb Merge pull request #214 from rust-ammonia/release-4.1.1
  • 262d0d3 Release 4.1.1
  • 84e7284 Merge pull request #213 from rust-ammonia/dependabot/cargo/html5ever-0.35
  • f5ad1ec Add bool flag to mark scripting as disabled
  • 00aac0f Update html5ever requirement from 0.31 to 0.35
  • Additional commits viewable in compare view

Updates time from 0.3.36 to 0.3.47

Release notes

Sourced from time's releases.

v0.3.47

See the changelog for details.

v0.3.46

See the changelog for details.

v0.3.45

See the changelog for details.

v0.3.44

See the changelog for details.

v0.3.43

See the changelog for details.

v0.3.42

See the changelog for details.

v0.3.41

See the changelog for details.

v0.3.40

See the changelog for details.

v0.3.39

See the changelog for details.

v0.3.38

See the changelog for details.

v0.3.37

See the changelog for details.

Changelog

Sourced from time's changelog.

0.3.47 [2026-02-05]

Security

  • The possibility of a stack exhaustion denial of service attack when parsing RFC 2822 has been eliminated. Previously, it was possible to craft input that would cause unbounded recursion. Now, the depth of the recursion is tracked, causing an error to be returned if it exceeds a reasonable limit.

    This attack vector requires parsing user-provided input, with any type, using the RFC 2822 format.

Compatibility

  • Attempting to format a value with a well-known format (i.e. RFC 3339, RFC 2822, or ISO 8601) will error at compile time if the type being formatted does not provide sufficient information. This would previously fail at runtime. Similarly, attempting to format a value with ISO 8601 that is only configured for parsing (i.e. Iso8601::PARSING) will error at compile time.

Added

  • Builder methods for format description modifiers, eliminating the need for verbose initialization when done manually.
  • date!(2026-W01-2) is now supported. Previously, a space was required between W and 01.
  • [end] now has a trailing_input modifier which can either be prohibit (the default) or discard. When it is discard, all remaining input is ignored. Note that if there are components after [end], they will still attempt to be parsed, likely resulting in an error.

Changed

  • More performance gains when parsing.

Fixed

  • If manually formatting a value, the number of bytes written was one short for some components. This has been fixed such that the number of bytes written is always correct.
  • The possibility of integer overflow when parsing an owned format description has been effectively eliminated. This would previously wrap when overflow checks were disabled. Instead of storing the depth as u8, it is stored as u32. This would require multiple gigabytes of nested input to overflow, at which point we've got other problems and trivial mitigations are available by downstream users.

0.3.46 [2026-01-23]

Added

  • All possible panics are now documented for the relevant methods.
  • The need to use #[serde(default)] when using custom serde formats is documented. This applies only when deserializing an Option<T>.
  • Duration::nanoseconds_i128 has been made public, mirroring std::time::Duration::from_nanos_u128.

... (truncated)

Commits
  • d5144cd v0.3.47 release
  • f6206b0 Guard against integer overflow in release mode
  • 1c63dc7 Avoid denial of service when parsing Rfc2822
  • 5940df6 Add builder methods to avoid verbose construction
  • 00881a4 Manually format macros everywhere
  • bb723b6 Add trailing_input modifier to end
  • 31c4f8e Permit W12 in date! macro
  • 490a17b Mark error paths in well-known formats as cold
  • 6cb1896 Optimize Rfc2822 parsing
  • 6d264d5 Remove erroneous #[inline(never)] attributes
  • Additional commits viewable in compare view

Updates tracing-subscriber from 0.3.18 to 0.3.20

Release notes

Sourced from tracing-subscriber's releases.

tracing-subscriber 0.3.20

Security Fix: ANSI Escape Sequence Injection (CVE-TBD)

Impact

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

Solution

Version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.

Affected Versions

All versions of tracing-subscriber prior to 0.3.20 are affected by this vulnerability.

Recommendations

Immediate Action Required: We recommend upgrading to tracing-subscriber 0.3.20 immediately, especially if your application:

  • Logs user-provided input (form data, HTTP headers, query parameters, etc.)
  • Runs in environments where terminal output is displayed to users

Migration

This is a patch release with no breaking API changes. Simply update your Cargo.toml:

[dependencies]
tracing-subscriber = "0.3.20"

Acknowledgments

We would like to thank zefr0x who responsibly reported the issue at security@tokio.rs.

If you believe you have found a security vulnerability in any tokio-rs project, please email us at security@tokio.rs.

tracing-subscriber 0.3.19

[ [crates.io][crate-0.3.19] ] | [ [docs.rs][docs-0.3.19] ]

This release updates the tracing dependency to [v0.1.41][tracing-0.1.41] and the tracing-serde dependency to [v0.2.0][tracing-serde-0.2.0].

Added

... (truncated)

Commits

Updates time from 0.3.36 to 0.3.47

Release notes

Sourced from time's releases.

v0.3.47

See the changelog for details.

v0.3.46

See the changelog for details.

v0.3.45

See the changelog for details.

v0.3.44

See the changelog for details.

v0.3.43

See the changelog for details.

v0.3.42

See the changelog for details.

v0.3.41

See the changelog for details.

v0.3.40

See the changelog for details.

v0.3.39

See the changelog for details.

v0.3.38

See the changelog for details.

v0.3.37

See the changelog for details.

Changelog

Sourced from time's changelog.

0.3.47 [2026-02-05]

Security

  • The possibility of a stack exhaustion denial of service attack when parsing RFC 2822 has been eliminated. Previously, it was possible to craft input that would cause unbounded recursion. Now, the depth of the recursion is tracked, causing an error to be returned if it exceeds a reasonable limit.

    This attack vector requires parsing user-provided input, with any type, using the RFC 2822 format.

Compatibility

  • Attempting to format a value with a well-known format (i.e. RFC 3339, RFC 2822, or ISO 8601) will error at compile time if the type being formatted does not provide sufficient information. This would previously fail at runtime. Similarly, attempting to format a value with ISO 8601 that is only configured for parsing (i.e. Iso8601::PARSING) will error at compile time.

Added

  • Builder methods for format description modifiers, eliminating the need for verbose initialization when done manually.
  • date!(2026-W01-2) is now supported. Previously, a space was required between W and 01.
  • [end] now has a trailing_input modifier which can either be prohibit (the default) or discard. When it is discard, all remaining input is ignored. Note that if there are components after [end], they will still attempt to be parsed, likely resulting in an error.

Changed

  • More performance gains when parsing.

Fixed

  • If manually formatting a value, the number of bytes written was one short for some components. This has been fixed such that the number of bytes written is always correct.
  • The possibility of integer overflow when parsing an owned format description has been effectively eliminated. This would previously wrap when overflow checks were disabled. Instead of storing the depth as u8, it is stored as u32. This would require multiple gigabytes of nested input to overflow, at which point we've got other problems and trivial mitigations are available by downstream users.

0.3.46 [2026-01-23]

Added

  • All possible panics are now documented for the relevant methods.
  • The need to use #[serde(default)] when using custom serde formats is documented. This applies only when deserializing an Option<T>.
  • Duration::nanoseconds_i128 has been made public, mirroring std::time::Duration::from_nanos_u128.

... (truncated)

Commits
  • d5144cd v0.3.47 release
  • f6206b0 Guard against integer overflow in release mode
  • 1c63dc7 Avoid denial of service when parsing Rfc2822
  • 5940df6 Add builder methods to avoid verbose construction
  • 00881a4 Manually format macros everywhere
  • bb723b6 Add trailing_input modifier to end
  • 31c4f8e Permit W12 in date! macro
  • 490a17b Mark error paths in well-known formats as cold
  • 6cb1896 Optimize Rfc2822 parsing
  • 6d264d5 Remove erroneous #[inline(never)] attributes
  • Additional commits viewable in compare view

Updates crossbeam-channel from 0.5.13 to 0.5.15

Release notes

Sourced from crossbeam-channel's releases.

crossbeam-channel 0.5.15

  • Fix regression introduced in 0.5.12 that can lead to a double free when dropping unbounded channel. (#1187)

crossbeam-channel 0.5.14

  • Fix stack overflow when sending large value to unbounded channel. (#1146, #1147)
  • Add Select::new_biased function. (#1150)
  • Remove inefficient spinning. (#1154)
  • Suppress buggy clippy::zero_repeat_side_effects lint in macro generated code. (#1123)
Commits
  • d35ffde Prepare for the next release
  • 6ec74ec crossbeam-channel: prevent double free on Drop (#1187)
  • ccd83ac Prepare for the next release
  • 54988eb Calculate layout in const context
  • 761d0b6 Port #1146 & #1147 to deque::Injector and queue::SegQueue
  • 8144fbb Remove optimistic spinning from Context::wait_until
  • a92f6c4 Bump peter-evans/create-pull-request from 5 to 7 (#1153)
  • 66d41a9 channel: Add new_biased constructor for biased channel selection (#1150)
  • d0d0a80 CachePadded: Use 128-byte alignment on arm64ec
  • f757eef Add comment about fixed rustc bug
  • Additional commits viewable in compare view

Updates tracing-subscriber from 0.3.18 to 0.3.19

Release notes

Sourced from tracing-subscriber's releases.

tracing-subscriber 0.3.20

Security Fix: ANSI Escape Sequence Injection (CVE-TBD)

Impact

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

Solution

Version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.

Affected Versions

All versions of tracing-subscriber prior to 0.3.20 are affected by this vulnerability.

Recommendations

Immediate Action Required: We recommend upgrading to tracing-subscriber 0.3.20 immediately, especially if your application:

  • Logs user-provided input (form data, HTTP headers, query parameters, etc.)
  • Runs in environments where terminal output is displayed to users

Migration

This is a patch release with no breaking API changes. Simply update your Cargo.toml:

[dependencies]
tracing-subscriber = "0.3.20"

Acknowledgments

We would like to thank zefr0x who responsibly reported the issue at security@tokio.rs.

If you believe you have found a security vulnerability in any tokio-rs project, please email us at security@tokio.rs.

tracing-subscriber 0.3.19

[ [crates.io][crate-0.3.19] ] | [ [docs.rs][docs-0.3.19] ]

This release updates the tracing dependency to [v0.1.41][tracing-0.1.41] and the tracing-serde dependency to [v0.2.0][tracing-serde-0.2.0].

Added

... (truncated)

Commits

Updates crossbeam-channel from 0.5.13 to 0.5.15

Release notes

Sourced from crossbeam-channel's releases.

crossbeam-channel 0.5.15

  • Fix regression introduced in 0.5.12 that can lead to a double free when dropping unbounded channel. (#1187)

crossbeam-channel 0.5.14

  • Fix stack overflow when sending large value to unbounded channel. (#1146, #1147)
  • Add Select::new_biased function. (#1150)
  • Remove inefficient spinning. (#1154)
  • Suppress buggy clippy::zero_repeat_side_effects lint in macro generated code. (#1123)
Commits
  • d35ffde Prepare for the next release
  • 6ec74ec crossbeam-channel: prevent double free on Drop (#1187)
  • ccd83ac Prepare for the next release
  • 54988eb Calculate layout in const context
  • 761d0b6 Port #1146 & #1147 to deque::Injector and queue::SegQueue
  • 8144fbb Remove optimistic spinning from Context::wait_until
  • a92f6c4 Bump peter-evans/create-pull-request from 5 to 7 (#1153)
  • 66d41a9 channel: Add new_biased constructor for biased channel selection (#1150)
  • d0d0a80 CachePadded: Use 128-byte alignment on arm64ec
  • f757eef Add comment about fixed rustc bug
  • Additional commits viewable in compare view

Updates rustix from 0.38.8 to 0.38.44

Commits

Updates ammonia from 4.0.0 to 4.0.1

Release notes

Sourced from ammonia's releases.

4.1.2

  • fix: unexpected namespace switches after cleanup can cause mXSS (reported by zzm0902@shu.edu.cn)

4.1.1

4.1.0

  • chore: bump MSRV to 1.80.0
  • chore: switch to std's LazyLock instead of once_cell's Lazy
  • feature: improve panic message when clean_content_tags conflicts with other options
  • feature: add support for sanitizing the style attribute

4.0.1

  • fix: unexpected namespace switches after cleanup can cause mXSS (reported by zzm0902@shu.edu.cn, backport 4.1.2)
Changelog

Sourced from ammonia's changelog.

4.1.2

  • fix: unexpected namespace switches after cleanup can cause mXSS (reported by zzm0902@shu.edu.cn)

4.1.1

4.1.0

  • chore: bump MSRV to 1.80.0
  • chore: switch to std's LazyLock instead of once_cell's Lazy
  • feature: improve panic message when clean_content_tags conflicts with other options
  • feature: add support for sanitizing the style attribute

4.0.1

  • fix: unexpected namespace switches after cleanup can cause mXSS (backport 4.1.2)
Commits
  • de02971 Release 4.1.2 with security fix
  • 7e9754b Merge pull request #218 from atouchet/trav
  • f1e732c Delete .travis.yml
  • 5d54a86 Merge pull request #216 from atouchet/urls
  • 52a7d97 Update Readme
  • a14a5eb Merge pull request #214 from rust-ammonia/release-4.1.1
  • 262d0d3 Release 4.1.1
  • 84e7284 Merge pull request #213 from rust-ammonia/dependabot/cargo/html5ever-0.35
  • f5ad1ec Add bool flag to mark scripting as disabled
  • 00aac0f Update html5ever requirement from 0.31 to 0.35
  • Additional commits viewable in compare view

Updates time from 0.3.36 to 0.3.47

Release notes

Sourced from time's releases.

v0.3.47

See the changelog for details.

v0.3.46

See the changelog for details.

v0.3.45

See the changelog for details.

v0.3.44

See the changelog for details.

v0.3.43

See the changelog for details.

v0.3.42

See the changelog for details.

v0.3.41

See the changelog for details.

v0.3.40

See the changelog for details.

v0.3.39

See the changelog for details.

v0.3.38

See the changelog for details.

v0.3.37

See the changelog for details.

Changelog

Sourced from time's changelog.

0.3.47 [2026-02-05]

Security

  • The possibility of a stack exhaustion denial of service attack when parsing RFC 2822 has been eliminated. Previously, it was possible to craft input that would cause unbounded recursion. Now, the depth of the recursion is tracked, causing an error to be returned if it exceeds a reasonable limit.

    This attack vector requires parsing user-provided input, with any type, using the RFC 2822 format.

Compatibility

  • Attempting to format a value with a well-known format (i.e. RFC 3339, RFC 2822, or ISO 8601) will error at compile time if the type being formatted does not provide sufficient information. This would previously fail at runtime. Similarly, attempting to format a value with ISO 8601 that is only configured for parsing (i.e. Iso8601::PARSING) will error at compile time.

Added

  • Builder methods for format description modifiers, eliminating the need for verbose initialization when done manually.
  • date!(2026-W01-2) is now supported. Previously, a space was required between W and 01.
  • [end] now has a trailing_input modifier which can either be prohibit (the default) or discard. When it is discard, all remaining input is ignored. Note that if there are components after [end], they will still attempt to be parsed, likely resulting in an error.

Changed

  • More performance gains when parsing.

Fixed

  • If manually formatting a value, the number of bytes written was one short for some components. This has been fixed such that the number of bytes written is always correct.
  • The possibility of integer overflow when parsing an owned format description has been effectively eliminated. This would previously wrap when overflow checks were disabled. Instead of storing the depth as u8, it is stored as u32. This would require multiple gigabytes of nested input to overflow, at which point we've got other problems and trivial mitigations are available by downstream users.

0.3.46 [2026-01-23]

Added

  • All possible panics are now documented for the relevant methods.
  • The need to use #[serde(default)] when using custom serde formats is documented. This applies only when deserializing an Option<T>.
  • Duration::nanoseconds_i128 has been made public, mirroring std::time::Duration::from_nanos_u128.

... (truncated)

Commits
  • d5144cd v0.3.47 release
  • f6206b0 Guard against integer overflow in release mode
  • 1c63dc7 Avoid denial of service when parsing Rfc2822
  • 5940df6 Add builder methods to avoid verbose construction
  • 00881a4 Manually format macros everywhere
  • bb723b6 Add trailing_input modifier to end
  • 31c4f8e Permit W12 in date! macro
  • 490a17b Mark error paths in well-known formats as cold
  • 6cb1896 Optimize Rfc2822 parsing
  • 6d264d5 Remove erroneous #[inline(never)] attributes
  • Additional commits viewable in compare view

Updates crossbeam-channel from 0.5.13 to 0.5.15

Release notes

Sourced from crossbeam-channel's releases.

crossbeam-channel 0.5.15

  • Fix regression introduced in 0.5.12 that can lead to a double free when dropping unbounded channel. (#1187)

crossbeam-channel 0.5.14

  • Fix stack overflow when sending large value to unbounded channel. (#1146, #1147)
  • Add Select::new_biased function. (#1150)
  • Remove inefficient spinning. (#1154)
  • Suppress buggy clippy::zero_repeat_side_effects lint in macro generated code. (#1123)
Commits
  • d35ffde Prepare for the next release
  • 6ec74ec crossbeam-channel: prevent double free on Drop (#1187)
  • ccd83ac Prepare for the next release
  • 54988eb Calculate layout in const context
  • 761d0b6 Port #1146 & #1147 to deque::Injector and queue::SegQueue
  • 8144fbb Remove optimistic spinning from Context::wait_until
  • a92f6c4 Bump peter-evans/create-pull-request from 5 to 7 (#1153)
  • 66d41a9 channel: Add new_biased constructor for biased channel selection (#1150)
  • d0d0a80 CachePadded: Use 128-byte alignment on arm64ec
  • f757eef Add comment about fixed rustc bug
  • Additional commits viewable in compare view

Updates tokio from 1.38.0 to 1.38.2

Release notes

Sourced from tokio's releases.

Tokio v1.38.2

This release fixes a soundness issue in the broadcast channel. The channel accepts values that are Send but !Sync. Previously, the channel called clone() on these values without synchronizing. This release fixes the channel by synchronizing calls to .clone() (Thanks Austin Bonander for finding and reporting the issue).

Fixed

  • sync: synchronize clone() call in broadcast channel (#7232)

#7232: tokio-rs/tokio#7232

Tokio v1.38.1

1.38.1 (July 16th, 2024)

This release fixes the bug identified as (#6682), which caused timers not to fire when they should.

Fixed

  • time: update wake_up while holding all the locks of sharded time wheels (#6683)

#6682: tokio-rs/tokio#6682 #6683: tokio-rs/tokio#6683

Commits

Updates bytes from 1.6.0 to 1.11.1

Release notes

Sourced from bytes's releases.

Bytes v1.11.1

1.11.1 (February 3rd, 2026)

  • Fix integer overflow in BytesMut::reserve

Bytes v1.11.0

1.11.0 (November 14th, 2025)

  • Bump MSRV to 1.57 (#788)

Fixed

  • fix: BytesMut only reuse if src has remaining (#803)
  • Specialize BytesMut::put::<Bytes> (#793)
  • Reserve capacity in BytesMut::put (#794)
  • Change BytesMut::remaining_mut to use isize::MAX instead of usize::MAX (#795)

Internal changes

  • Guarantee address in slice() for empty slices. (#780)
  • Rename Vtable::to_* -> Vtable::into_* (#776)
  • Fix latest clippy warnings (#787)
  • Ignore BytesMut::freeze doctest on wasm (#790)
  • Move drop_fn of from_owner into vtable (#801)

Bytes v1.10.1

1.10.1 (March 5th, 2025)

Fixed

  • Fix memory leak when using to_vec with Bytes::from_owner (#773)

#773: tokio-rs/bytes#773

Bytes v1.10.0

1.10.0 (February 3rd, 2025)

Added

  • Add feature to support platforms without atomic CAS (#467)
  • try_get_* methods for Buf trait (#753)
  • Implement Buf::chunks_vectored for Take (#617)
  • Implement Buf::chunks_vectored for VecDeque<u8> (#708)

Fixed

  • Remove incorrect guarantee for chunks_vectored (#754)
  • Ensure that tests pass under panic=abort (#749)

... (truncated)

Changelog

Sourced from bytes's changelog.

1.11.1 (February 3rd, 2026)

  • Fix integer overflow in BytesMut::reserve

1.11.0 (November 14th, 2025)

  • ...

    Description has been truncated

@dependabot
Bump the cargo group across 6 directories with 9 updates
ea8e917 
Bumps the cargo group with 1 update in the /src/tools/rustfmt directory: [tracing-subscriber](https://github.com/tokio-rs/tracing).
Bumps the cargo group with 2 updates in the /src/tools/rustbook directory: [ammonia](https://github.com/rust-ammonia/ammonia) and [time](https://github.com/time-rs/time).
Bumps the cargo group with 3 updates in the /src/tools/rust-analyzer directory: [tracing-subscriber](https://github.com/tokio-rs/tracing), [time](https://github.com/time-rs/time) and [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam).
Bumps the cargo group with 2 updates in the /src/tools/miri directory: [tracing-subscriber](https://github.com/tokio-rs/tracing) and [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam).
Bumps the cargo group with 1 update in the /compiler/rustc_codegen_gcc directory: [rustix](https://github.com/bytecodealliance/rustix).
Bumps the cargo group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [ammonia](https://github.com/rust-ammonia/ammonia) | `4.0.0` | `4.0.1` |
| [time](https://github.com/time-rs/time) | `0.3.36` | `0.3.47` |
| [crossbeam-channel](https://github.com/crossbeam-rs/crossbeam) | `0.5.13` | `0.5.15` |
| [tokio](https://github.com/tokio-rs/tokio) | `1.38.0` | `1.38.2` |
| [bytes](https://github.com/tokio-rs/bytes) | `1.6.0` | `1.11.1` |
| [zerovec](https://github.com/unicode-org/icu4x) | `0.10.2` | `0.10.4` |
| [zerovec-derive](https://github.com/unicode-org/icu4x) | `0.10.2` | `0.10.3` |



Updates `tracing-subscriber` from 0.3.17 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.17...tracing-subscriber-0.3.20)

Updates `ammonia` from 4.0.0 to 4.1.2
- [Release notes](https://github.com/rust-ammonia/ammonia/releases)
- [Changelog](https://github.com/rust-ammonia/ammonia/blob/master/CHANGELOG.md)
- [Commits](rust-ammonia/ammonia@v4.0.0...v4.1.2)

Updates `time` from 0.3.36 to 0.3.47
- [Release notes](https://github.com/time-rs/time/releases)
- [Changelog](https://github.com/time-rs/time/blob/main/CHANGELOG.md)
- [Commits](time-rs/time@v0.3.36...v0.3.47)

Updates `tracing-subscriber` from 0.3.18 to 0.3.20
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.17...tracing-subscriber-0.3.20)

Updates `time` from 0.3.36 to 0.3.47
- [Release notes](https://github.com/time-rs/time/releases)
- [Changelog](https://github.com/time-rs/time/blob/main/CHANGELOG.md)
- [Commits](time-rs/time@v0.3.36...v0.3.47)

Updates `crossbeam-channel` from 0.5.13 to 0.5.15
- [Release notes](https://github.com/crossbeam-rs/crossbeam/releases)
- [Changelog](https://github.com/crossbeam-rs/crossbeam/blob/master/CHANGELOG.md)
- [Commits](crossbeam-rs/crossbeam@crossbeam-channel-0.5.13...crossbeam-channel-0.5.15)

Updates `tracing-subscriber` from 0.3.18 to 0.3.19
- [Release notes](https://github.com/tokio-rs/tracing/releases)
- [Commits](tokio-rs/tracing@tracing-subscriber-0.3.17...tracing-subscriber-0.3.20)

Updates `crossbeam-channel` from 0.5.13 to 0.5.15
- [Release notes](https://github.com/crossbeam-rs/crossbeam/releases)
- [Changelog](https://github.com/crossbeam-rs/crossbeam/blob/master/CHANGELOG.md)
- [Commits](crossbeam-rs/crossbeam@crossbeam-channel-0.5.13...crossbeam-channel-0.5.15)

Updates `rustix` from 0.38.8 to 0.38.44
- [Release notes](https://github.com/bytecodealliance/rustix/releases)
- [Changelog](https://github.com/bytecodealliance/rustix/blob/main/CHANGES.md)
- [Commits](bytecodealliance/rustix@v0.38.8...v0.38.44)

Updates `ammonia` from 4.0.0 to 4.0.1
- [Release notes](https://github.com/rust-ammonia/ammonia/releases)
- [Changelog](https://github.com/rust-ammonia/ammonia/blob/master/CHANGELOG.md)
- [Commits](rust-ammonia/ammonia@v4.0.0...v4.1.2)

Updates `time` from 0.3.36 to 0.3.47
- [Release notes](https://github.com/time-rs/time/releases)
- [Changelog](https://github.com/time-rs/time/blob/main/CHANGELOG.md)
- [Commits](time-rs/time@v0.3.36...v0.3.47)

Updates `crossbeam-channel` from 0.5.13 to 0.5.15
- [Release notes](https://github.com/crossbeam-rs/crossbeam/releases)
- [Changelog](https://github.com/crossbeam-rs/crossbeam/blob/master/CHANGELOG.md)
- [Commits](crossbeam-rs/crossbeam@crossbeam-channel-0.5.13...crossbeam-channel-0.5.15)

Updates `tokio` from 1.38.0 to 1.38.2
- [Release notes](https://github.com/tokio-rs/tokio/releases)
- [Commits](tokio-rs/tokio@tokio-1.38.0...tokio-1.38.2)

Updates `bytes` from 1.6.0 to 1.11.1
- [Release notes](https://github.com/tokio-rs/bytes/releases)
- [Changelog](https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md)
- [Commits](tokio-rs/bytes@v1.6.0...v1.11.1)

Updates `zerovec` from 0.10.2 to 0.10.4
- [Release notes](https://github.com/unicode-org/icu4x/releases)
- [Changelog](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md)
- [Commits](https://github.com/unicode-org/icu4x/commits/ind/zerovec@0.10.4)

Updates `zerovec-derive` from 0.10.2 to 0.10.3
- [Release notes](https://github.com/unicode-org/icu4x/releases)
- [Changelog](https://github.com/unicode-org/icu4x/blob/main/CHANGELOG.md)
- [Commits](https://github.com/unicode-org/icu4x/commits/ind/zerovec-derive@0.10.3)

---
updated-dependencies:
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: ammonia
  dependency-version: 4.1.2
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: time
  dependency-version: 0.3.47
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: tracing-subscriber
  dependency-version: 0.3.20
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: time
  dependency-version: 0.3.47
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: crossbeam-channel
  dependency-version: 0.5.15
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: tracing-subscriber
  dependency-version: 0.3.19
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: crossbeam-channel
  dependency-version: 0.5.15
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: rustix
  dependency-version: 0.38.44
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: ammonia
  dependency-version: 4.0.1
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: time
  dependency-version: 0.3.47
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: crossbeam-channel
  dependency-version: 0.5.15
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: tokio
  dependency-version: 1.38.2
  dependency-type: direct:production
  dependency-group: cargo
- dependency-name: bytes
  dependency-version: 1.11.1
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: zerovec
  dependency-version: 0.10.4
  dependency-type: indirect
  dependency-group: cargo
- dependency-name: zerovec-derive
  dependency-version: 0.10.3
  dependency-type: indirect
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Mar 4, 2026
@dependabot @github

dependabot Bot commented on behalf of github Mar 20, 2026

Copy link
Copy Markdown
Author

Superseded by #3.

@dependabot dependabot Bot closed this Mar 20, 2026
@dependabot
dependabot Bot deleted the dependabot/cargo/src/tools/rustfmt/cargo-f1a3f38cc9 branch March 20, 2026 18:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants