Skip to content

build(deps): bump the rust group across 1 directory with 13 updates - #186

Open
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/cargo/rust-d31ec0f1c8
Open

build(deps): bump the rust group across 1 directory with 13 updates#186
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/cargo/rust-d31ec0f1c8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 20, 2026

Copy link
Copy Markdown
Contributor

Bumps the rust group with 10 updates in the / directory:

Package From To
base64 0.23.0 0.23.1
blake3 1.8.5 1.8.6
bstr 1.13.0 1.13.1
clap 4.6.5 4.6.6
comfy-table 7.2.2 8.0.0
futures 0.3.33 0.3.34
moka 0.12.15 0.12.16
thiserror 2.0.19 2.0.20
whoami 2.1.2 2.1.3
zerocopy 0.8.55 0.8.56

Updates base64 from 0.23.0 to 0.23.1

Changelog

Sourced from base64's changelog.

0.23.1

  • Make the tests build again on non-SIMD architectures
Commits

Updates blake3 from 1.8.5 to 1.8.6

Release notes

Sourced from blake3's releases.

1.8.6

version 1.8.6

Changes since 1.8.5:

  • update_mmap and update_mmap_rayon (and by extension b3sum) now use seek rather than metadata to get the length of a file/mapping, and they tolerate mmap failures. That means b3sum will now memory map e.g. Linux block devices, which support mapping despite reporting length 0 in metadata. Hashing NUL files on Windows also works now, where previously it was an error unless you used --no-mmap or <. This change was originally proposed by @​nabijaczleweli.
Commits

Updates bstr from 1.13.0 to 1.13.1

Commits

Updates clap from 4.6.5 to 4.6.6

Release notes

Sourced from clap's releases.

v4.6.6

[4.6.6] - 2026-08-06

Features

  • Add Command::get_overridden_usage
Changelog

Sourced from clap's changelog.

[4.6.6] - 2026-08-06

Features

  • Add Command::get_overridden_usage
Commits
  • 348cff3 chore: Release
  • d478377 docs: Update changelog
  • 04b9fbb Merge pull request #6414 from koopatroopa787/fix-bash-completion-bracket-glob
  • 7075239 Merge pull request #6422 from BaumiCoder/fix-fish-indentations
  • f90a966 fix(complete): Use spaces for indentation in fish
  • dd4997b fix(complete): Don't glob-expand bash positionals
  • 8387c81 Merge pull request #6399 from clap-rs/renovate/crate-ci-typos-1.x
  • 8141e11 chore(deps): Update compatible (dev) (#6398)
  • 8a6bd4e chore(deps): Update pre-commit hook crate-ci/typos to v1.47.0
  • 71a7213 chore(deps): Update Rust Stable to v1.96 (#6396)
  • See full diff in compare view

Updates comfy-table from 7.2.2 to 8.0.0

Release notes

Sourced from comfy-table's releases.

v8.0.0

[8.0.0] - 05.08.2026

Breaking Changes

  • The following types and functions have been removed:

    • TableComponent enum
    • The modifiers module and Table::apply_modifier have been removed.
    • Table::current_style_as_preset
    • Table::set_style
    • Table::style
    • Table::remove_style
    • Table::load_preset
  • The positional preset string format has been replaced with the new TableStyle, LineStyle and ContentLineStyle types. The old approach of having "stringified" presets was too finicky and also implicitly bound to the order of variants in the old TableComponent enum. It was just not a good design.

    The new design, in comparison, has a nice and (hopefully) intuitive API to define a style. On top of that, all functions on TableStyle are const, so custom styles can still be declared as constants:

    const MY_STYLE: TableStyle = TableStyle::new()
        .top_border(LineStyle::new('┌', '─', '┬', '┐'))
        .header_lines(ContentLineStyle::new('│', '┆', '│'))
        .header_separator(LineStyle::new('╞', '═', '╪', '╡'))
        .content_lines(ContentLineStyle::new('│', '┆', '│'))
        .bottom_border(LineStyle::new('└', '─', '┴', '┘'));

    The new API looks as follows:

    • Presets in comfy_table::presets::* are now TableStyle constants.
    • Table::load_style(style) has been added to load a preset or custom style.
    • Table::style() and Table::style_mut() to get a handle to the style used by the table. The mut handle can be used to change the style.
    • Instead of modifiers, there are now functions on TableStyle TableStyle::with_rounded_corners/TableStyle::with_solid_inner_borders.
    • All fields of TableStyle, LineStyle and ContentLineStyle are public:
      table.style_mut().top_border.left = Some('╭');
  • The default truncation indicator is now instead of .... This should make it more obvious that there's more text and consumes less visual space.

Fix

  • Various performance improvements that reduce table formatting time quite a bit:

    • ~36% for "normal" tables (The readme of the project). 17µs -> 11µs
    • ~34% for "larger" tables, which I would consider a reasonable usecase. 253µs -> 172µs
    • ~70% for very large tables, i.e. a 10x500 table. -> 20.8ms -> 6.15ms

    Most of these improvements boil down to:

... (truncated)

Changelog

Sourced from comfy-table's changelog.

[8.0.0] - 05.08.2026

Breaking Changes

  • The following types and functions have been removed:

    • TableComponent enum
    • The modifiers module and Table::apply_modifier have been removed.
    • Table::current_style_as_preset
    • Table::set_style
    • Table::style
    • Table::remove_style
    • Table::load_preset
  • The positional preset string format has been replaced with the new TableStyle, LineStyle and ContentLineStyle types. The old approach of having "stringified" presets was too finicky and also implicitly bound to the order of variants in the old TableComponent enum. It was just not a good design.

    The new design, in comparison, has a nice and (hopefully) intuitive API to define a style. On top of that, all functions on TableStyle are const, so custom styles can still be declared as constants:

    const MY_STYLE: TableStyle = TableStyle::new()
        .top_border(LineStyle::new('┌', '─', '┬', '┐'))
        .header_lines(ContentLineStyle::new('│', '┆', '│'))
        .header_separator(LineStyle::new('╞', '═', '╪', '╡'))
        .content_lines(ContentLineStyle::new('│', '┆', '│'))
        .bottom_border(LineStyle::new('└', '─', '┴', '┘'));

    The new API looks as follows:

    • Presets in comfy_table::presets::* are now TableStyle constants.
    • Table::load_style(style) has been added to load a preset or custom style.
    • Table::style() and Table::style_mut() to get a handle to the style used by the table. The mut handle can be used to change the style.
    • Instead of modifiers, there are now functions on TableStyle TableStyle::with_rounded_corners/TableStyle::with_solid_inner_borders.
    • All fields of TableStyle, LineStyle and ContentLineStyle are public:
      table.style_mut().top_border.left = Some('╭');
  • The default truncation indicator is now instead of .... This should make it more obvious that there's more text and consumes less visual space.

Fix

  • Various performance improvements that reduce table formatting time quite a bit:

    • ~36% for "normal" tables (The readme of the project). 17µs -> 11µs
    • ~34% for "larger" tables, which I would consider a reasonable usecase. 253µs -> 172µs
    • ~70% for very large tables, i.e. a 10x500 table. -> 20.8ms -> 6.15ms

    Most of these improvements boil down to:

    • Less string allocations.

... (truncated)

Commits
  • cf91e01 chore: Release comfy-table version 8.0.0
  • 38f044c chore: Prepare release
  • 401171a refactor: Replace old presets with TableStyle
  • f4be04a chore: Fix and extend lints
  • 1bdfda2 perf: Don't allocate strings when splitting
  • 36bd44f perf: Track line width in split_line
  • 212099c perf: Optimize border handling in draw_rows
  • a968011 perf: Cut down string allocations in align_line
  • fea164e perf: Move formatted lines instead of cloning them
  • 2935d4e perf: Add printable-ASCII fast path to split_long_word
  • Additional commits viewable in compare view

Updates futures from 0.3.33 to 0.3.34

Release notes

Sourced from futures's releases.

0.3.34

  • Preserve cloned waker identity. (#3032)
  • Updato syn to 3. (#3028)
Changelog

Sourced from futures's changelog.

0.3.34 - 2026-08-11

  • Preserve cloned waker identity. (#3032)
  • Updato syn to 3. (#3028)
Commits

Updates futures-core from 0.3.33 to 0.3.34

Release notes

Sourced from futures-core's releases.

0.3.34

  • Preserve cloned waker identity. (#3032)
  • Updato syn to 3. (#3028)
Changelog

Sourced from futures-core's changelog.

0.3.34 - 2026-08-11

  • Preserve cloned waker identity. (#3032)
  • Updato syn to 3. (#3028)
Commits

Updates futures-sink from 0.3.33 to 0.3.34

Release notes

Sourced from futures-sink's releases.

0.3.34

  • Preserve cloned waker identity. (#3032)
  • Updato syn to 3. (#3028)
Changelog

Sourced from futures-sink's changelog.

0.3.34 - 2026-08-11

  • Preserve cloned waker identity. (#3032)
  • Updato syn to 3. (#3028)
Commits

Updates futures-util from 0.3.33 to 0.3.34

Release notes

Sourced from futures-util's releases.

0.3.34

  • Preserve cloned waker identity. (#3032)
  • Updato syn to 3. (#3028)
Changelog

Sourced from futures-util's changelog.

0.3.34 - 2026-08-11

  • Preserve cloned waker identity. (#3032)
  • Updato syn to 3. (#3028)
Commits

Updates moka from 0.12.15 to 0.12.16

Release notes

Sourced from moka's releases.

v0.12.16

Version 0.12.16

Fixed

  • Fixed a bug where cache eviction could stall permanently when the cache was configured with the non-default LRU eviction policy (EvictionPolicy::lru()) by a race between insert and remove operations on the same key (#592gh-pull-0592 by @​kim-jhyeon, reported in #590gh-issue-0590):
    • This bug was introduced in v0.12.0 and affected sync::Cache, sync::SegmentedCache and future::Cache.
    • A race between applying a write recording for an entry and concurrently removing that entry from the internal concurrent hash table could leave an orphaned node at the front of the LRU queue. Once present, no entry was ever evicted again and the cache grew unboundedly past max_capacity.
    • The same race also affected the default TinyLFU eviction policy, but with a milder symptom: each occurrence permanently leaked one phantom entry slot, causing entry_count and weighted_size to over-report and the usable capacity to shrink by one entry per occurrence. Fixed by the same change.

Changed

  • Worked around a ThreadSanitizer false positive (#602gh-pull-0602):
    • Replaced the standalone fence(Acquire) in the internal MiniArc's drop path with an Acquire load of the reference count, so that downstream projects can now run ThreadSanitizer on code using Moka without hitting this false positive.
    • std::sync::Arc has a similar workaround.
  • Raised the minimum version of the crossbeam-epoch crate from v0.9.18 to v0.9.20 to avoid the following advisory (#603gh-pull-0603):
    • [RUSTSEC-2026-0204] crossbeam-epoch: invalid pointer dereference in fmt::Pointer for Atomic and Shared
    • Moka is not affected by this advisory because it never formats these pointer types. However, raising the minimum version prevents downstream lockfiles from resolving to an affected crossbeam-epoch version via Moka.
Changelog

Sourced from moka's changelog.

Version 0.12.16

Fixed

  • Fixed a bug where cache eviction could stall permanently when the cache was configured with the non-default LRU eviction policy (EvictionPolicy::lru()) by a race between insert and remove operations on the same key (#592[gh-pull-0592] by [@​kim-jhyeon][gh-kim-jhyeon], reported in #590[gh-issue-0590]):
    • This bug was introduced in v0.12.0 and affected sync::Cache, sync::SegmentedCache and future::Cache.
    • A race between applying a write recording for an entry and concurrently removing that entry from the internal concurrent hash table could leave an orphaned node at the front of the LRU queue. Once present, no entry was ever evicted again and the cache grew unboundedly past max_capacity.
    • The same race also affected the default TinyLFU eviction policy, but with a milder symptom: each occurrence permanently leaked one phantom entry slot, causing entry_count and weighted_size to over-report and the usable capacity to shrink by one entry per occurrence. Fixed by the same change.

Changed

  • Worked around a ThreadSanitizer false positive (#602[gh-pull-0602]):
    • Replaced the standalone fence(Acquire) in the internal MiniArc's drop path with an Acquire load of the reference count, so that downstream projects can now run ThreadSanitizer on code using Moka without hitting this false positive.
    • std::sync::Arc has a similar workaround.
  • Raised the minimum version of the crossbeam-epoch crate from v0.9.18 to v0.9.20 to avoid the following advisory (#603[gh-pull-0603]):
    • [RUSTSEC-2026-0204] crossbeam-epoch: invalid pointer dereference in fmt::Pointer for Atomic and Shared
    • Moka is not affected by this advisory because it never formats these pointer types. However, raising the minimum version prevents downstream lockfiles from resolving to an affected crossbeam-epoch version via Moka.
Commits
  • a616ec1 Merge pull request #604 from moka-rs/chore/bump-v0.12.16
  • 3b140a6 Bump the version to v0.12.16
  • 51b802d Merge pull request #603 from moka-rs/bump-crossbeam-epoch-floor
  • 4f90716 Raise the minimum crossbeam-epoch version to 0.9.20
  • 08d0e04 Merge pull request #602 from moka-rs/gh600-tsan-workaround
  • 14447a7 Restructure the v0.12.16 TSan workaround CHANGELOG entry
  • 7b14c37 Avoid a TSan false positive by replacing the fence in MiniArc::drop
  • 05b37c6 Merge pull request #599 from moka-rs/gh590-deterministic-tests
  • fc31858 Replace private doc references in gh590 test comments
  • 5743592 Improve the v0.12.16 CHANGELOG entry
  • Additional commits viewable in compare view

Updates thiserror from 2.0.19 to 2.0.20

Release notes

Sourced from thiserror's releases.

2.0.20

  • Suppress redundant_field_names clippy lint in generated code (#454)
Commits

Updates whoami from 2.1.2 to 2.1.3

Release notes

Sourced from whoami's releases.

v2.1.3

Changelog

Added

  • Support for detecting the Mate desktop environment

Changed

  • Bumped minimum version of dependencies libc and libredox to latest (libc 0.2.189, libredox 0.1.19)

What's Changed

New Contributors

Full Changelog: ardaku/whoami@v2.1.2...v2.1.3

Commits

Updates zerocopy from 0.8.55 to 0.8.56

Release notes

Sourced from zerocopy's releases.

v0.8.56

What's Changed

New Contributors

Full Changelog: google/zerocopy@v0.8.55...v0.8.56

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

NotAShelf and others added 2 commits August 20, 2026 08:49
Signed-off-by: NotAShelf <raf@notashelf.dev>
Change-Id: I1791c63cad6dc1e20778f3a5c43de6496a6a6964
Bumps the rust group with 10 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [base64](https://github.com/marshallpierce/rust-base64) | `0.23.0` | `0.23.1` |
| [blake3](https://github.com/BLAKE3-team/BLAKE3) | `1.8.5` | `1.8.6` |
| [bstr](https://github.com/BurntSushi/bstr) | `1.13.0` | `1.13.1` |
| [clap](https://github.com/clap-rs/clap) | `4.6.5` | `4.6.6` |
| [comfy-table](https://github.com/nukesor/comfy-table) | `7.2.2` | `8.0.0` |
| [futures](https://github.com/rust-lang/futures-rs) | `0.3.33` | `0.3.34` |
| [moka](https://github.com/moka-rs/moka) | `0.12.15` | `0.12.16` |
| [thiserror](https://github.com/dtolnay/thiserror) | `2.0.19` | `2.0.20` |
| [whoami](https://github.com/ardaku/whoami) | `2.1.2` | `2.1.3` |
| [zerocopy](https://github.com/google/zerocopy) | `0.8.55` | `0.8.56` |



Updates `base64` from 0.23.0 to 0.23.1
- [Changelog](https://github.com/marshallpierce/rust-base64/blob/master/RELEASE-NOTES.md)
- [Commits](marshallpierce/rust-base64@v0.23.0...v0.23.1)

Updates `blake3` from 1.8.5 to 1.8.6
- [Release notes](https://github.com/BLAKE3-team/BLAKE3/releases)
- [Commits](BLAKE3-team/BLAKE3@1.8.5...1.8.6)

Updates `bstr` from 1.13.0 to 1.13.1
- [Commits](BurntSushi/bstr@1.13.0...1.13.1)

Updates `clap` from 4.6.5 to 4.6.6
- [Release notes](https://github.com/clap-rs/clap/releases)
- [Changelog](https://github.com/clap-rs/clap/blob/master/CHANGELOG.md)
- [Commits](clap-rs/clap@clap_complete-v4.6.5...clap_complete-v4.6.6)

Updates `comfy-table` from 7.2.2 to 8.0.0
- [Release notes](https://github.com/nukesor/comfy-table/releases)
- [Changelog](https://github.com/Nukesor/comfy-table/blob/main/CHANGELOG.md)
- [Commits](Nukesor/comfy-table@v7.2.2...v8.0.0)

Updates `futures` from 0.3.33 to 0.3.34
- [Release notes](https://github.com/rust-lang/futures-rs/releases)
- [Changelog](https://github.com/rust-lang/futures-rs/blob/main/CHANGELOG.md)
- [Commits](rust-lang/futures-rs@0.3.33...0.3.34)

Updates `futures-core` from 0.3.33 to 0.3.34
- [Release notes](https://github.com/rust-lang/futures-rs/releases)
- [Changelog](https://github.com/rust-lang/futures-rs/blob/main/CHANGELOG.md)
- [Commits](rust-lang/futures-rs@0.3.33...0.3.34)

Updates `futures-sink` from 0.3.33 to 0.3.34
- [Release notes](https://github.com/rust-lang/futures-rs/releases)
- [Changelog](https://github.com/rust-lang/futures-rs/blob/main/CHANGELOG.md)
- [Commits](rust-lang/futures-rs@0.3.33...0.3.34)

Updates `futures-util` from 0.3.33 to 0.3.34
- [Release notes](https://github.com/rust-lang/futures-rs/releases)
- [Changelog](https://github.com/rust-lang/futures-rs/blob/main/CHANGELOG.md)
- [Commits](rust-lang/futures-rs@0.3.33...0.3.34)

Updates `moka` from 0.12.15 to 0.12.16
- [Release notes](https://github.com/moka-rs/moka/releases)
- [Changelog](https://github.com/moka-rs/moka/blob/main/CHANGELOG.md)
- [Commits](moka-rs/moka@v0.12.15...v0.12.16)

Updates `thiserror` from 2.0.19 to 2.0.20
- [Release notes](https://github.com/dtolnay/thiserror/releases)
- [Commits](dtolnay/thiserror@2.0.19...2.0.20)

Updates `whoami` from 2.1.2 to 2.1.3
- [Release notes](https://github.com/ardaku/whoami/releases)
- [Commits](ardaku/whoami@v2.1.2...v2.1.3)

Updates `zerocopy` from 0.8.55 to 0.8.56
- [Release notes](https://github.com/google/zerocopy/releases)
- [Commits](google/zerocopy@v0.8.55...v0.8.56)

---
updated-dependencies:
- dependency-name: base64
  dependency-version: 0.23.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: blake3
  dependency-version: 1.8.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: bstr
  dependency-version: 1.13.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: clap
  dependency-version: 4.6.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: comfy-table
  dependency-version: 8.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: rust
- dependency-name: futures
  dependency-version: 0.3.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: futures-core
  dependency-version: 0.3.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: futures-sink
  dependency-version: 0.3.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: futures-util
  dependency-version: 0.3.34
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: moka
  dependency-version: 0.12.16
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: thiserror
  dependency-version: 2.0.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: whoami
  dependency-version: 2.1.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
- dependency-name: zerocopy
  dependency-version: 0.8.56
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: rust
...

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 Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant