8000 build(deps): bump the cargo group across 1 directory with 18 updates by dependabot[bot] · Pull Request #2230 · gominimal/minimal · GitHub
[go: up one dir, main page]

Skip to content

build(deps): bump the cargo group across 1 directory with 18 updates - #2230

Closed
dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/cargo/cargo-bfb95ec54c
Closed

dependabot[bot] wants to merge 2 commits into
mainfrom
dependabot/cargo/cargo-bfb95ec54c

Conversation

@dependabot
@dependabot dependabot Bot commented on behalf of github Oct 15, 2026 •
Copy link
Copy Markdown
Contributor

Bumps the cargo group with 18 updates in the / directory:

Package From To
arbitrary 1.4.2 1.5.0
either 1.18.0 1.19.0
indoc 2.0.7 2.0.8
insta 1.48.0 1.49.0
json-subscriber 0.3.0 0.3.1
opentelemetry-semantic-conventions 0.33.0 0.33.1
opentelemetry 0.33.0 0.33.1
opentelemetry_sdk 0.33.0 0.33.1
opentelemetry-http 0.33.0 0.33.1
opentelemetry-appender-tracing 0.33.0 0.33.1
proptest 1.11.0 1.12.0
russh 0.63.3 0.64.1
serde_json 1.0.151 1.0.154
sha2 0.11.0 0.11.1
smallvec 1.16.2 1.16.3
tokio 1.53.1 1.53.2
tokio-util 0.7.19 0.7.20
uuid 1.27.0 1.28.0

Updates arbitrary from 1.4.2 to 1.5.0

Changelog

Sourced from arbitrary's changelog.

1.5.0

Released 2026-10-05.

Added

  • Added support for deriving Arbitrary for types with raw identifiers.

Changed

  • Updated derive_arbitrary to syn 3. This raises the MSRV from 1.63.0 to 1.71.0, which is the MSRV of syn 3.

Fixed

  • Fixed soundness when generating arrays.
  • Fixed nonzero integer generation to always produce a nonzero value.
  • Updated derive_arbitrary to include fixes for fully qualified paths.

Commits
  • 9807b59 Merge pull request #243 from fitzgen/bump-to-1.5.0
  • 7a49e61 Bump to version 1.5.0
  • aa2802b Merge pull request #242 from drakeo338/claude/241-fix
  • a9f7ca5 Update derive_arbitrary to syn 3 and raise MSRV to 1.71
  • cd35bd2 Merge pull request #239 from Manishearth/fix-soundness
  • 53a651d agent-driven: Fix soundness in try_create_array
  • df8afe9 Merge pull request #238 from baloo/baloo/push-lopsmyosqnpv
  • 15f5c08 Bring fix for fully qualified path
  • 341a8fd Merge pull request #237 from ngildenhuys/downgrading_msrv_deps
  • 9b68ef4 ci: adding update commands to downgrade dependencies to fix MSRV test
  • Additional commits viewable in compare view

Updates either from 1.18.0 to 1.19.0

Changelog

Sourced from either's changelog.

Commits

Updates indoc from 2.0.7 to 2.0.8

Release notes

Sourced from indoc's releases.

2.0.8

Commits
  • 79ab4aa Release 2.0.8
  • 23804cf Touch up PR 70
  • 69d23e5 Merge pull request #70 from joshka/joshka/panicdoc
  • e769537 Add panicdoc macro
  • c75dfae Update ui test suite to nightly-2026-08-12
  • 8faf6fa Raise minimum tested compiler to rust 1.88
  • 77d569f Update actions/upload-artifact@v6 -> v7
  • 615b766 Update actions/checkout@v6 -> v7
  • 8ab5301 Lint clippy::from_iter_instead_of_collect has been removed
  • 7d85ef9 Raise minimum tested compiler to rust 1.85
  • Additional commits viewable in compare view

Updates insta from 1.48.0 to 1.49.0

Release notes

Sourced from insta's releases.

1.49.0

Release Notes

  • Allow Option<&OsStr> snapshot names, such as Path::file_name(), without explicit string conversion. #929 (@​dislogical)
  • Add prebuilt cargo-insta binaries for ARM64 Linux (aarch64-unknown-linux-gnu). #942 (@​aljohri)
  • Fix JSON serialization of maps keyed by unit enum variants. Keys use the serialized variant name, including serde renames. #934 (@​teddytennant)
  • Remove trailing semicolons from serialization macro bodies to avoid compiler warnings when used in expression position. #940 (@​Tiwalun)
  • Mention INSTA_UPDATE=always in snapshot mismatch hints for file snapshots. #927 (@​hiro-nikaitou)
  • Update the lockfile's tempfile and rustix dependencies to fix builds with newer Rust toolchains. #939
  • Fix cargo insta test --all-targets --test-runner nextest failing with "Can't mix --doc with other target selecting options". Like cargo test --all-targets, it no longer runs doctests. #460

Install cargo-insta 1.49.0

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/mitsuhiko/insta/releases/download/1.49.0/cargo-insta-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/mitsuhiko/insta/releases/download/1.49.0/cargo-insta-installer.ps1 | iex"

Download cargo-insta 1.49.0

File Platform Checksum
cargo-insta-aarch64-apple-darwin.tar.xz Apple Silicon macOS checksum
cargo-insta-x86_64-apple-darwin.tar.xz Intel macOS checksum
cargo-insta-x86_64-pc-windows-msvc.zip x64 Windows checksum
cargo-insta-aarch64-unknown-linux-gnu.tar.xz ARM64 Linux checksum
cargo-insta-x86_64-unknown-linux-gnu.tar.xz x64 Linux checksum
cargo-insta-x86_64-unknown-linux-musl.tar.xz x64 MUSL Linux checksum

This was written by Codex on behalf of @​max-sixty

Changelog

Sourced from insta's changelog.

1.49.0

  • Allow Option<&OsStr> snapshot names, such as Path::file_name(), without explicit string conversion. #929 (@​dislogical)
  • Add prebuilt cargo-insta binaries for ARM64 Linux (aarch64-unknown-linux-gnu). #942 (@​aljohri)
  • Fix JSON serialization of maps keyed by unit enum variants. Keys use the serialized variant name, including serde renames. #934 (@​teddytennant)
  • Remove trailing semicolons from serialization macro bodies to avoid compiler warnings when used in expression position. #940 (@​Tiwalun)
  • Mention INSTA_UPDATE=always in snapshot mismatch hints for file snapshots. #927 (@​hiro-nikaitou)
  • Update the lockfile's tempfile and rustix dependencies to fix builds with newer Rust toolchains. #939
  • Fix cargo insta test --all-targets --test-runner nextest failing with "Can't mix --doc with other target selecting options". Like cargo test --all-targets, it no longer runs doctests. #460
Commits
  • 5df39ce Release 1.49.0 (#944)
  • 1c28c19 Skip the separate doctest run for nextest with --all-targets (#941)
  • 064742e Build cargo-insta for aarch64-unknown-linux-gnu (#942)
  • 08b67d9 Remove trailing semicolons from macro bodies (#940)
  • 06858e1 fix: regenerate Cargo.lock to avoid broken rustix 0.37.27 (#939)
  • 70be034 Serialize unit enum variants used as JSON map keys (#934)
  • 54d0b96 feat: implement From for SnapshotValue with OsStr (#929)
  • 3d62572 [fix] Mention INSTA_UPDATE variable in snapshot mismatch errors (#927)
  • 1712876 ci: run CI on a pinned toolchain via rust-toolchain.toml; fix format-arg lint...
  • See full diff in compare view

Updates json-subscriber from 0.3.0 to 0.3.1

Release notes

Sourced from json-subscriber's releases.

v0.3.1

Added

  • Add support for tracing-opentelemetry 0.34 (#46)
  • Implement tracing valuable support (#44)
  • Expose with_opentelemetry_ids() for all supported versions (#45)
Changelog

Sourced from json-subscriber's changelog.

0.3.1 - 2026-10-05

Added

  • Add support for tracing-opentelemetry 0.34 (#46)
  • Implement tracing valuable support (#44)
  • Expose with_opentelemetry_ids() for all supported versions (#45)
Commits
  • 2443723 chore: release v0.3.1 (#47)
  • 392c686 Implement tracing valuable support (#44)
  • e7d8643 ci: fix criterion benchmark usage in CI
  • 4219d94 chore: fix clippy lint
  • 3b9dac4 fmt: Expose with_opentelemetry_ids() for all supported versions (#45)
  • d1e1372 Add support for tracing-opentelemetry 0.34 (#46)
  • See full diff in compare view

Updates opentelemetry-semantic-conventions from 0.33.0 to 0.33.1

Commits
  • 372ebbc chore: prepare 0.33.1 release and stabilize OTLP logs and metrics (#3782)
  • 5582e71 docs(logs): polish design doc and fill perf numbers (#3566)
  • 7ce1269 fix(sdk): log when the periodic metrics reader panics (#3777)
  • b547036 fix(prometheus): keep resource labels when scope info is disabled (#3751)
  • e8480db chore(deps): bump rust-toolchain from 1.98.0 to 1.99.0 (#3770)
  • 0fdfc48 feat(proto): Add support for protobuffer descriptor output (#3675)
  • 87929d7 ci: install markdown-link-check from npm (#3661)
  • ff2ab2d docs(trace): explain async context propagation (#3759)
  • 2595432 fix(proto): accept omitted default fields in OTLP/JSON exponential histogram,...
  • 952bdee fix: accept optional whitespace in TraceState (#3761)
  • Additional commits viewable in compare view

Updates opentelemetry from 0.33.0 to 0.33.1

Commits
  • 372ebbc chore: prepare 0.33.1 release and stabilize OTLP logs and metrics (#3782)
  • 5582e71 docs(logs): polish design doc and fill perf numbers (#3566)
  • 7ce1269 fix(sdk): log when the periodic metrics reader panics (#3777)
  • b547036 fix(prometheus): keep resource labels when scope info is disabled (#3751)
  • e8480db chore(deps): bump rust-toolchain from 1.98.0 to 1.99.0 (#3770)
  • 0fdfc48 feat(proto): Add support for protobuffer descriptor output (#3675)
  • 87929d7 ci: install markdown-link-check from npm (#3661)
  • ff2ab2d docs(trace): explain async context propagation (#3759)
  • 2595432 fix(proto): accept omitted default fields in OTLP/JSON exponential histogram,...
  • 952bdee fix: accept optional whitespace in TraceState (#3761)
  • Additional commits viewable in compare view

Updates opentelemetry_sdk from 0.33.0 to 0.33.1

Commits
  • 372ebbc chore: prepare 0.33.1 release and stabilize OTLP logs and metrics (#3782)
  • 5582e71 docs(logs): polish design doc and fill perf numbers (#3566)
  • 7ce1269 fix(sdk): log when the periodic metrics reader panics (#3777)
  • b547036 fix(prometheus): keep resource labels when scope info is disabled (#3751)
  • e8480db chore(deps): bump rust-toolchain from 1.98.0 to 1.99.0 (#3770)
  • 0fdfc48 feat(proto): Add support for protobuffer descriptor output (#3675)
  • 87929d7 ci: install markdown-link-check from npm (#3661)
  • ff2ab2d docs(trace): explain async context propagation (#3759)
  • 2595432 fix(proto): accept omitted default fields in OTLP/JSON exponential histogram,...
  • 952bdee fix: accept optional whitespace in TraceState (#3761)
  • Additional commits viewable in compare view

Updates opentelemetry-http from 0.33.0 to 0.33.1

Commits
  • 372ebbc chore: prepare 0.33.1 release and stabilize OTLP logs and metrics (#3782)
  • 5582e71 docs(logs): polish design doc and fill perf numbers (#3566)
  • 7ce1269 fix(sdk): log when the periodic metrics reader panics (#3777)
  • b547036 fix(prometheus): keep resource labels when scope info is disabled (#3751)
  • e8480db chore(deps): bump rust-toolchain from 1.98.0 to 1.99.0 (#3770)
  • 0fdfc48 feat(proto): Add support for protobuffer descriptor output (#3675)
  • 87929d7 ci: install markdown-link-check from npm (#3661)
  • ff2ab2d docs(trace): explain async context propagation (#3759)
  • 2595432 fix(proto): accept omitted default fields in OTLP/JSON exponential histogram,...
  • 952bdee fix: accept optional whitespace in TraceState (#3761)
  • Additional commits viewable in compare view

Updates opentelemetry-appender-tracing from 0.33.0 to 0.33.1

Commits
  • 372ebbc chore: prepare 0.33.1 release and stabilize OTLP logs and metrics (#3782)
  • 5582e71 docs(logs): polish design doc and fill perf numbers (#3566)
  • 7ce1269 fix(sdk): log when the periodic metrics reader panics (#3777)
  • b547036 fix(prometheus): keep resource labels when scope info is disabled (#3751)
  • e8480db chore(deps): bump rust-toolchain from 1.98.0 to 1.99.0 (#3770)
  • 0fdfc48 feat(proto): Add support for protobuffer descriptor output (#3675)
  • 87929d7 ci: install markdown-link-check from npm (#3661)
  • ff2ab2d docs(trace): explain async context propagation (#3759)
  • 2595432 fix(proto): accept omitted default fields in OTLP/JSON exponential histogram,...
  • 952bdee fix: accept optional whitespace in TraceState (#3761)
  • Additional commits viewable in compare view

Updates proptest from 1.11.0 to 1.12.0

Commits
  • 70cf37d Merge pull request #675 from proptest-rs/prep-1.12
  • 729e0ff prepare next releases and fix panic handling
  • 28c1fad Merge pull request #664 from Expyron/main
  • 5ddd9a4 Merge pull request #668 from toddATavail/fix-fork-persisted-failure
  • a6a9ac7 Merge pull request #673 from glaziermag/fix-book-deploy
  • d57d88b Replace rand_chacha with chacha20
  • 9411213 Deploy the book on pushes to main
  • 1719745 fix: terminate the fork replay when a persisted failure fails
  • 0f55b7a test: a persisted failure in a forked test must be reported
  • 4b0594e Merge pull request #669 from proptest-rs/no-fail-fast
  • Additional commits viewable in compare view

Updates russh from 0.63.3 to 0.64.1

Release notes

Sourced from russh's releases.

v0.64.1

Security fixes

GHSA-4wc5-f2rc-q74m - Unbounded memory allocation in agent protocol server via crafted constraint records

A local actor or a connected remote server (that the user forwards an agent connection to) can trigger an unlimited memory allocation in a russh-based SSH agent via a crafted message.

v0.64.0

Breaking changes

  • 5d9d2b8: drop the legacy ed25519 key parser
    • Dropped the legacy-ed25519-pkcs8-parser feature. Legacy keys were written in non-compliant format by russh pre-v0.43. From now on, parsing those keys will return a hard error.

Security fixes

GHSA-j7h2-66j4-ghjf - russh server accepts pubkey authentication with a mismatched signature algorithm

Russh server side did not verify that the client signatures were made using the negotiated algorithm. While no bypass is possible through this bug, this allowed a client to e.g. silently downgrade its own signature from rsa-sha2-512 to rsa-sha1

Features

  • efa9a03: Add support hostkeys-prove-00@openssh.com support (#767) (@​inureyes) #767

    • Adds client::Handle::hostkeys_prove to ask the server to prove ownership of the host keys it announced via hostkeys-00@openssh.com.
  • a0ded76: Support sending custom global requests from the client (#759) (@​ChrisJr404) #759

    • Adds client::Handle::send_global_request(name, data, want_reply)

Fixes

New Contributors

Full Changelog: Eugeny/russh@v0.63.3...v0.64.0

Commits

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

v1.0.153

v1.0.152

Commits
  • 20572a6 Release 1.0.154
  • a91bfaf Fix RandomState links in map documentation
  • 3c932c0 Merge pull request #1333 from razmser/no-std-preserve-order
  • 4b2d726 Release 1.0.153
  • 83335ee Touch up PR 1345
  • 4b4810a Resolve range_plus_one pedantic clippy lint
  • 8af71cc Merge pull request #1345 from 00200200/fix-invalid-utf8-error-column
  • 452afa2 Correct multiline raw UTF-8 error positions and simplify indexing
  • c9f1e3b Release 1.0.152
  • 854fc70 Touch up PR 1347
  • Additional commits viewable in compare view

Updates sha2 from 0.11.0 to 0.11.1

Commits

Updates smallvec from 1.16.2 to 1.16.3

Release notes

Sourced from smallvec's releases.

v1.16.3

What's Changed

Full Changelog: smallvec/smallvec@v1.16.2...v1.16.3

Commits

Updates tokio from 1.53.1 to 1.53.2

Release notes

Sourced from tokio's releases.

Tokio v1.53.2

1.53.2 (October 3rd, 2026)

Fixed

  • fs: handle integer overflow in buffered relative seek (#8574)
  • io: revert "always cleanup AsyncFd registration list on deregister" (#8540)
  • process: unregister Windows wait before closing child handle (#8564)
  • rt: drop blocking pool mutex before shutting down rejected task (#8562)
  • sync: fix mpsc index wraparound in block reclamation (#8546)
  • sync: forget mpsc Permit before sending value (#8560)
  • sync: validate MAX_PERMITS in Semaphore::acquire (#8548)
  • sync: wake broadcast Sender::closed outside mutex (#8558)
  • task: drop replaced waker outside lock in JoinSet (#8554)
  • time: drop timer lock before dropping waker in clear_entry (#8552)
  • time: expire timers directly on shutdown without rotating wheel (#8570)

Fixed (unstable)

  • fs: clamp io_uring read length to u32::MAX (#8572)
  • rt: ignore current_thread task dumps from other runtimes (#8544)
  • rt: preserve io_uring context if a completion waker panics (#8566)
  • sync: fix semaphore use-after-free and permit leak on tracing panic (#8542)
  • taskdump: restore deferred leaf wakes during capture (#8445)
  • time: drop stored waker when cancelling alt timer entry (#8550)

#8445: tokio-rs/tokio#8445 #8572: tokio-rs/tokio#8572 #8540: tokio-rs/tokio#8540 #8542: tokio-rs/tokio#8542 #8544: tokio-rs/tokio#8544 #8546: tokio-rs/tokio#8546 #8548: tokio-rs/tokio#8548 #8550: tokio-rs/tokio#8550 #8552: tokio-rs/tokio#8552 #8554: tokio-rs/tokio#8554 #8558: tokio-rs/tokio#8558 #8560: tokio-rs/tokio#8560 #8562: tokio-rs/tokio#8562 #8564: tokio-rs/tokio#8564 #8566: tokio-rs/tokio#8566 #8570: tokio-rs/tokio#8570 #8574: tokio-rs/tokio#8574

Commits
  • ff0c406 chore: prepare Tokio v1.53.2 (#8580)
  • a762700 Merge 'tokio-1.51.5' into 'tokio-1.53.x' (#8577)
  • ec31a9f chore: prepare Tokio v1.51.5 (#8579)
  • 625c851 sync: assign semaphore permits before emitting tracing event (#8542)
  • 832dd23 sync: avoid leaking semaphore permits on tracing panic (#8542)
  • 826954a sync: unlink semaphore waiter before emitting tracing event (#8542)
  • 9a47992 process: unregister Windows wait before closing child handle (#8564)
  • 2fc5972 fs: handle integer overflow in buffered relative seek (#8574)
  • 85a6d13 io: revert "always cleanup AsyncFd registration list on deregister" (#8540)
  • 436faa2 rt: drop blocking pool mutex before shutting down rejected task (#8562)
  • Additional commits viewable in compare view

Updates tokio-util from 0.7.19 to 0.7.20

Commits

Bumps the cargo group with 18 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [arbitrary](https://github.com/rust-fuzz/arbitrary) | `1.4.2` | `1.5.0` |
| [either](https://github.com/rayon-rs/either) | `1.18.0` | `1.19.0` |
| [indoc](https://github.com/dtolnay/indoc) | `2.0.7` | `2.0.8` |
| [insta](https://github.com/mitsuhiko/insta) | `1.48.0` | `1.49.0` |
| [json-subscriber](https://github.com/mladedav/json-subscriber) | `0.3.0` | `0.3.1` |
| [opentelemetry-semantic-conventions](https://github.com/open-telemetry/opentelemetry-rust) | `0.33.0` | `0.33.1` |
| [opentelemetry](https://github.com/open-telemetry/opentelemetry-rust) | `0.33.0` | `0.33.1` |
| [opentelemetry_sdk](https://github.com/open-telemetry/opentelemetry-rust) | `0.33.0` | `0.33.1` |
| [opentelemetry-http](https://github.com/open-telemetry/opentelemetry-rust) | `0.33.0` | `0.33.1` |
| [opentelemetry-appender-tracing](https://github.com/open-telemetry/opentelemetry-rust) | `0.33.0` | `0.33.1` |
| [proptest](https://github.com/proptest-rs/proptest) | `1.11.0` | `1.12.0` |
| [russh](https://github.com/warp-tech/russh) | `0.63.3` | `0.64.1` |
| [serde_json](https://github.com/serde-rs/json) | `1.0.151` | `1.0.154` |
| [sha2](https://github.com/RustCrypto/hashes) | `0.11.0` | `0.11.1` |
| [smallvec](https://github.com/servo/rust-smallvec) | `1.16.2` | `1.16.3` |
| [tokio](https://github.com/tokio-rs/tokio) | `1.53.1` | `1.53.2` |
| [tokio-util](https://github.com/tokio-rs/tokio) | `0.7.19` | `0.7.20` |
| [uuid](https://github.com/uuid-rs/uuid) | `1.27.0` | `1.28.0` |



Updates `arbitrary` from 1.4.2 to 1.5.0
- [Changelog](https://github.com/rust-fuzz/arbitrary/blob/main/CHANGELOG.md)
- [Commits](rust-fuzz/arbitrary@v1.4.2...v1.5.0)

Updates `either` from 1.18.0 to 1.19.0
- [Changelog](https://github.com/rayon-rs/either/blob/main/RELEASES.md)
- [Commits](rayon-rs/either@1.18.0...1.19.0)

Updates `indoc` from 2.0.7 to 2.0.8
- [Release notes](https://github.com/dtolnay/indoc/releases)
- [Commits](dtolnay/indoc@2.0.7...2.0.8)

Updates `insta` from 1.48.0 to 1.49.0
- [Release notes](https://github.com/mitsuhiko/insta/releases)
- [Changelog](https://github.com/mitsuhiko/insta/blob/master/CHANGELOG.md)
- [Commits](mitsuhiko/insta@1.48.0...1.49.0)

Updates `json-subscriber` from 0.3.0 to 0.3.1
- [Release notes](https://github.com/mladedav/json-subscriber/releases)
- [Changelog](https://github.com/mladedav/json-subscriber/blob/main/CHANGELOG.md)
- [Commits](mladedav/json-subscriber@json-subscriber-v0.3.0...json-subscriber-v0.3.1)

Updates `opentelemetry-semantic-conventions` from 0.33.0 to 0.33.1
- [Release notes](https://github.com/open-telemetry/opentelemetry-rust/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.32.md)
- [Commits](open-telemetry/opentelemetry-rust@opentelemetry-semantic-conventions-0.33.0...opentelemetry-semantic-conventions-0.33.1)

Updates `opentelemetry` from 0.33.0 to 0.33.1
- [Release notes](https://github.com/open-telemetry/opentelemetry-rust/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.32.md)
- [Commits](open-telemetry/opentelemetry-rust@opentelemetry-0.33.0...opentelemetry-0.33.1)

Updates `opentelemetry_sdk` from 0.33.0 to 0.33.1
- [Release notes](https://github.com/open-telemetry/opentelemetry-rust/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.32.md)
- [Commits](open-telemetry/opentelemetry-rust@opentelemetry_sdk-0.33.0...opentelemetry_sdk-0.33.1)

Updates `opentelemetry-http` from 0.33.0 to 0.33.1
- [Release notes](https://github.com/open-telemetry/opentelemetry-rust/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.32.md)
- [Commits](open-telemetry/opentelemetry-rust@opentelemetry-http-0.33.0...opentelemetry-http-0.33.1)

Updates `opentelemetry-appender-tracing` from 0.33.0 to 0.33.1
- [Release notes](https://github.com/open-telemetry/opentelemetry-rust/releases)
- [Changelog](https://github.com/open-telemetry/opentelemetry-rust/blob/main/docs/release_0.32.md)
- [Commits](open-telemetry/opentelemetry-rust@opentelemetry-appender-tracing-0.33.0...opentelemetry-appender-tracing-0.33.1)

Updates `proptest` from 1.11.0 to 1.12.0
- [Release notes](https://github.com/proptest-rs/proptest/releases)
- [Changelog](https://github.com/proptest-rs/proptest/blob/main/CHANGELOG.md)
- [Commits](proptest-rs/proptest@v1.11.0...v1.12.0)

Updates `russh` from 0.63.3 to 0.64.1
- [Release notes](https://github.com/warp-tech/russh/releases)
- [Commits](Eugeny/russh@v0.63.3...v0.64.1)

Updates `serde_json` from 1.0.151 to 1.0.154
- [Release notes](https://github.com/serde-rs/json/releases)
- [Commits](serde-rs/json@v1.0.151...v1.0.154)

Updates `sha2` from 0.11.0 to 0.11.1
- [Commits](RustCrypto/hashes@sha2-v0.11.0...sha2-v0.11.1)

Updates `smallvec` from 1.16.2 to 1.16.3
- [Release notes](https://github.com/servo/rust-smallvec/releases)
- [Commits](smallvec/smallvec@v1.16.2...v1.16.3)

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

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

Updates `uuid` from 1.27.0 to 1.28.0
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.27.0...v1.28.0)

---
updated-dependencies:
- dependency-name: arbitrary
  dependency-version: 1.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo
- dependency-name: either
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo
- dependency-name: indoc
  dependency-version: 2.0.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: insta
  dependency-version: 1.49.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo
- dependency-name: json-subscriber
  dependency-version: 0.3.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: opentelemetry-semantic-conventions
  dependency-version: 0.33.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: opentelemetry
  dependency-version: 0.33.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: opentelemetry_sdk
  dependency-version: 0.33.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: opentelemetry-http
  dependency-version: 0.33.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: opentelemetry-appender-tracing
  dependency-version: 0.33.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: proptest
  dependency-version: 1.12.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo
- dependency-name: russh
  dependency-version: 0.64.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo
- dependency-name: serde_json
  dependency-version: 1.0.154
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: sha2
  dependency-version: 0.11.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: smallvec
  dependency-version: 1.16.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: tokio
  dependency-version: 1.53.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: tokio-util
  dependency-version: 0.7.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: cargo
- dependency-name: uuid
  dependency-version: 1.28.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: cargo
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from a team as a code owner October 15, 2026 22:33
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Oct 15, 2026
@coderabbitai
coderabbitai Bot commented Oct 15, 2026 •
Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: dbf8d1a2-28b9-41ec-8191-2832e1e04277

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

@minimal-foundry
minimal-foundry Bot commented Oct 15, 2026 •
Copy link
Copy Markdown
Contributor

Reviewed: 1 finding, none blocking at a2303e362336.

Address the comments on the diff.

Clobber: none: git log shows no recent fix reverted.

@minimal-foundry minimal-foundry Bot left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correctness

minimal-review — approved

Verdict APPROVE — No findings.

supply-chain

minimal-review — advisory review

Verdict COMMENT — 3 findings, 3 inline.

Panel: 2 of 3 personas ran (correctness, supply-chain); did not complete: security.

Comment thread Cargo.toml Resolved
Comment thread Cargo.lock
Comment on lines +5669 to +5672
"chacha20 0.10.2",
"core_detect",
"num-traits",
"rand 0.9.5",
"rand_chacha",
"rand 0.10.3",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOW · supply-chain · confidence 0.55 · in proptest

The proptest 1.11 -> 1.12 bump is not a routine patch: it transitively adds a sizeable new dependency subtree to the tree — borsh 1.8.1 with borsh-derive and proc-macro-crate (a full derive-driven serialization framework), core_detect, rand 0.10.3 (replacing rand 0.9.5), rand_xorshift 0.5.0, and chacha20 0.10.2, and moves bit-set/bit-vec to 0.11/0.10. None of borsh, borsh-derive, proc-macro-crate or core_detect existed in the base lock. The blast radius is contained — proptest is a dev-dependency of crates/minimald only (the NET-071 proxy property tests) — but the two things a maintainer should eyeball before merge are (1) that cargo-deny's unused-allowed-license = "deny" gate still passes: borsh is Apache-2.0/MIT and fine, while the license of the newly added core_detect crate could not be verified from this sandbox; and (2) that pulling a serialization framework into the dev graph is acceptable. If it is not desired, the proptest bump could be excluded from the group update.

What the reviewer checked

Cargo.lock proptest 1.12.0 deps: "chacha20 0.10.2", "core_detect", "rand 0.10.3"; new packages borsh 1.8.1 / borsh-derive / proc-macro-crate absent from base.

Hand this to an agent
Act on a code-review finding.

File:       Cargo.lock
Lines:      5669-5672
Category:   supply-chain
Severity:   low (reviewer confidence 0.55)

Finding:
The proptest 1.11 -> 1.12 bump is not a routine patch: it transitively adds a sizeable new dependency subtree to the tree — borsh 1.8.1 with borsh-derive and proc-macro-crate (a full derive-driven serialization framework), core_detect, rand 0.10.3 (replacing rand 0.9.5), rand_xorshift 0.5.0, and chacha20 0.10.2, and moves bit-set/bit-vec to 0.11/0.10. None of borsh, borsh-derive, proc-macro-crate or core_detect existed in the base lock. The blast radius is contained — proptest is a dev-dependency of crates/minimald only (the NET-071 proxy property tests) — but the two things a maintainer should eyeball before merge are (1) that cargo-deny's `unused-allowed-license = "deny"` gate still passes: borsh is Apache-2.0/MIT and fine, while the license of the newly added core_detect crate could not be verified from this sandbox; and (2) that pulling a serialization framework into the dev graph is acceptable. If it is not desired, the proptest bump could be excluded from the group update.

First verify this against the code yourself. It is model output and
may be wrong. If it is wrong, or the tradeoff was deliberate, say so
and change nothing.

👍 useful · 👎 noise — react to tell the reviewer. Replying works too, and says more.

Comment thread Cargo.lock
dependencies = [
"fastrand",
"getrandom 0.4.3",
"getrandom 0.3.4",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOW · supply-chain · confidence 0.55 · in tempfile

Silent change to what executes, worth a deliberate look before merge: the tempfile package entry (same version 3.27.0 and same checksum as the base) now depends on getrandom 0.3.4 where the base lockfile had getrandom 0.4.3. tempfile is used pervasively across the workspace for scratch files, and getrandom is the crate that sources OS entropy (RDRAND / the getrandom syscall), so this downgrades the entropy dependency for a widely-used crate while its version is unchanged. This is almost certainly resolver churn from the same cargo update re-resolution rather than an author decision, and 0.3.4 is a maintained line, so there is likely nothing to fix — but the change is invisible in the update list, and whoever merges should be comfortable that the downgrade is intended. If it is not wanted, pinning or excluding the offending bump would restore 0.4.3.

What the reviewer checked

Cargo.lock:7389 "getrandom 0.3.4", inside the tempfile 3.27.0 entry; base had "getrandom 0.4.3" for the identical tempfile version/checksum.

Hand this to an agent
Act on a code-review finding.

File:       Cargo.lock
Lines:      7389-7389
Category:   supply-chain
Severity:   low (reviewer confidence 0.55)

Finding:
Silent change to what executes, worth a deliberate look before merge: the tempfile package entry (same version 3.27.0 and same checksum as the base) now depends on getrandom 0.3.4 where the base lockfile had getrandom 0.4.3. tempfile is used pervasively across the workspace for scratch files, and getrandom is the crate that sources OS entropy (RDRAND / the getrandom syscall), so this downgrades the entropy dependency for a widely-used crate while its version is unchanged. This is almost certainly resolver churn from the same `cargo update` re-resolution rather than an author decision, and 0.3.4 is a maintained line, so there is likely nothing to fix — but the change is invisible in the update list, and whoever merges should be comfortable that the downgrade is intended. If it is not wanted, pinning or excluding the offending bump would restore 0.4.3.

First verify this against the code yourself. It is model output and
may be wrong. If it is wrong, or the tradeoff was deliberate, say so
and change nothing.

👍 useful · 👎 noise — react to tell the reviewer. Replying works too, and says more.

tokio 1.53.3 deprecates AsyncFd::new as unsound: it cannot prove that
the fd stays open and unchanged while the AsyncFd lives
(tokio-rs/tokio#8587). With clippy's -D warnings the deprecation fails
the build.

Both call sites, the PTY master and the tap device, now call
AsyncFd::register. Each SAFETY comment states why the fd stays valid:
the AsyncFd owns the File, and nothing reaches it to close or replace
the fd.
@minimal-foundry minimal-foundry Bot left a comment
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correctness

minimal-review — approved

Verdict APPROVE — No findings.

security

minimal-review — approved

Verdict APPROVE — No findings.

supply-chain

minimal-review — advisory review

Verdict COMMENT — 1 finding, 1 inline.

Panel: 3 of 3 personas ran (correctness, security, supply-chain).

Comment thread Cargo.lock
[[package]]
name = "tokio"
version = "1.53.1"
version = "1.53.3"
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOW · supply-chain · confidence 0.65

The lockfile resolves tokio at 1.53.3, above the 1.53.2 the PR body declares, and that is not a routine patch from a supply-chain standpoint: tokio 1.53.3 deprecates AsyncFd::new as unsound (tokio-rs/tokio#8587), which is what forced the hand-added head commit to switch the SSH daemon's PTY-master and tap paths from AsyncFd::new to unsafe AsyncFd::register. A dependency bump framed as '18 routine updates' thus changed what the daemon executes at two call sites, and the merged lockfile differs from the version the Dependabot description reviewed. A supply-chain reviewer should sign off explicitly that the merged state runs tokio 1.53.3, not the declared 1.53.2, before it is merged as a 'build(deps)' change.

What the reviewer checked

Cargo.lock:7623 version = "1.53.3" (PR body table: tokio 1.53.1 -> 1.53.2); commit a2303e3: 'tokio 1.53.3 deprecates AsyncFd::new as unsound' -> 'Both call sites ... now call AsyncFd::register'.

Hand this to an agent
Act on a code-review finding.

File:       Cargo.lock
Lines:      7623-7623
Category:   supply-chain
Severity:   low (reviewer confidence 0.65)

Finding:
The lockfile resolves tokio at 1.53.3, above the 1.53.2 the PR body declares, and that is not a routine patch from a supply-chain standpoint: tokio 1.53.3 deprecates `AsyncFd::new` as unsound (tokio-rs/tokio#8587), which is what forced the hand-added head commit to switch the SSH daemon's PTY-master and tap paths from `AsyncFd::new` to `unsafe AsyncFd::register`. A dependency bump framed as '18 routine updates' thus changed what the daemon executes at two call sites, and the merged lockfile differs from the version the Dependabot description reviewed. A supply-chain reviewer should sign off explicitly that the merged state runs tokio 1.53.3, not the declared 1.53.2, before it is merged as a 'build(deps)' change.

First verify this against the code yourself. It is model output and
may be wrong. If it is wrong, or the tradeoff was deliberate, say so
and change nothing.

👍 useful · 👎 noise — react to tell the reviewer. Replying works too, and says more.

@bryan-minimal
Copy link
Copy Markdown
Member

Superseded: this branch predates main's module renames (#2228), so it no longer applies. The same 18 updates, with Norrie's AsyncFd commit carried onto the renamed file, are up as a PR on main; dependabot closes this one when main's Cargo.toml moves.

@dependabot @github
dependabot Bot commented on behalf of github Oct 19, 2026
Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Oct 19, 2026
@dependabot
dependabot Bot deleted the dependabot/cargo/cargo-bfb95ec54c branch October 19, 2026 14:02
bryan-minimal added a commit that referenced this pull request Oct 22, 2026
evanspearman pushed a commit to evanspearman/minimal that referenced this pull request Oct 23, 2026
… on main (gominimal#2326)

* build(deps): the cargo group bump of gominimal#2230 (russh 0.64.1 and 17 others) on main

* fix(minimald): build AsyncFd with tokio's unsafe register

tokio 1.53.3 deprecates AsyncFd::new as unsound: it cannot prove that
the fd stays open and unchanged while the AsyncFd lives
(tokio-rs/tokio#8587). With clippy's -D warnings the deprecation fails
the build.

Both call sites, the PTY master and the tap device, now call
AsyncFd::register. Each SAFETY comment states why the fd stays valid:
the AsyncFd owns the File, and nothing reaches it to close or replace
the fd.

* build(deps): sha2 0.11.1 in the lock, as main has it, after the rebase

The group bump's lock still named sha2 0.11.0, which main's sign-in work
had moved on from; merged, the lock no longer matched the manifests and
the merge queue's --locked builds refused it.

---------

Co-authored-by: Norrie Taylor <norrie@minimal.dev>
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.

2 participants

0