chore(deps): bump the cargo-deps group across 1 directory with 8 updates

[dependabot]

Bumps the cargo-deps group with 8 updates in the / directory:

Package	From	To
tokio	1.51.1	1.52.1
axum	0.8.8	0.8.9
uuid	1.23.0	1.23.1
rustls	0.23.37	0.23.40
sentry	0.47.0	0.48.0
sentry-tracing	0.47.0	0.48.0
reqwest	0.13.2	0.13.3
redis	0.27.6	1.2.0

Updates tokio from 1.51.1 to 1.52.1

Release notes

Sourced from tokio's releases.

Tokio v1.52.1

1.52.1 (April 16th, 2026)

Fixed

• runtime: revert #7757 to fix [a regression]#8056 that causes spawn_blocking to hang (#8057)

#7757: tokio-rs/tokio#7757 #8056: tokio-rs/tokio#8056 #8057: tokio-rs/tokio#8057

Tokio v1.52.0

1.52.0 (April 14th, 2026)

Added

• io: AioSource::register_borrowed for I/O safety support (#7992)
• net: add try_io function to unix::pipe sender and receiver types (#8030)

Added (unstable)

• runtime: Builder::enable_eager_driver_handoff setting enable eager hand off of the I/O and time drivers before polling tasks (#8010)
• taskdump: add trace_with() for customized task dumps (#8025)
• taskdump: allow impl FnMut() in trace_with instead of just fn() (#8040)
• fs: support io_uring in AsyncRead for File (#7907)

Changed

• runtime: improve spawn_blocking scalability with sharded queue (#7757)
• runtime: use compare_exchange_weak() in worker queue (#8028)

Fixed

• runtime: overflow second half of tasks when local queue is filled instead of first half (#8029)

Documented

• docs: fix typo in oneshot::Sender::send docs (#8026)
• docs: hide #[tokio::main] attribute in the docs of sync::watch (#8035)
• net: add docs on ConnectionRefused errors with UDP sockets (#7870)

#7757: tokio-rs/tokio#7757 #7870: tokio-rs/tokio#7870 #7907: tokio-rs/tokio#7907 #7992: tokio-rs/tokio#7992 #8010: tokio-rs/tokio#8010 #8025: tokio-rs/tokio#8025 #8026: tokio-rs/tokio#8026 #8028: tokio-rs/tokio#8028 #8029: tokio-rs/tokio#8029

... (truncated)

Commits

• 905c146 chore: prepare to release v1.52.1 (#8059)
• 56aaa43 rt: revert #7757 to fix regression in spawn_blocking (#8057)
• 57ff47a ci: update trybuild to expect output from rustc 1.95.0 (#8058)
• 812de3e ci: bump taiki-e/cache-cargo-install-action from 1 to 3 (#8053)
• ba82e73 ci: use Dependabot to keep github actions up to date (#8052)
• 2e85f9d ci: replace cirrus-ci with freebsd-vm (#8041)
• a7e1cd8 ci: update GitHub Actions workflows to use latest tool versions (#8047)
• 5f7be0a chore: perpare 1.52.0 (#8045)
• 36d12d2 taskdump: allow impl FnMut() in taskdumps instead of just fn() (#8040)
• f943312 fs: support io-uring in AsyncRead for File (#7907)
• Additional commits viewable in compare view

Updates axum from 0.8.8 to 0.8.9

Release notes

Sourced from axum's releases.

axum-v0.8.9

• added: WebSocketUpgrade::{requested_protocols, set_selected_protocol} for more flexible subprotocol selection (#3597)
• changed: Update minimum rust version to 1.80 (#3620)
• fixed: Set connect endpoint on correct field in MethodRouter (#3656)
• fixed: Return specific error message when multipart body limit is exceeded (#3611)

#3597: tokio-rs/axum#3597 #3620: tokio-rs/axum#3620 #3656: tokio-rs/axum#3656 #3611: tokio-rs/axum#3611

Commits

• c59208c revert axum-core changelog changes
• 99068f5 Revert "Fix IntoResponse for tuples overriding error response codes (#3603)"
• 23d7098 Revert "axum-core 0.5.6"
• e8a39ad axum-macros 0.5.1
• 6e9a249 axum-extra 0.12.6
• 0ec9041 axum 0.8.9
• c3fcebb axum-core 0.5.6
• a8790fc update release notes
• 26ba7bb docs: consolidate state management docs in crate root (#3683)
• 9fc59ef Update to tokio-tungstenite 0.29 (#3689)
• Additional commits viewable in compare view

Updates uuid from 1.23.0 to 1.23.1

Release notes

Sourced from uuid's releases.

v1.23.1

What's Changed

• Remove deprecated msrv feature from wasm-bindgen dependency by @​guybedford in uuid-rs/uuid#877
• fix: Timestamp::from_gregorian deprecation note by @​aznashwan in uuid-rs/uuid#878
• Prepare for 1.23.1 release by @​KodrAus in uuid-rs/uuid#879

New Contributors

• @​guybedford made their first contribution in uuid-rs/uuid#877
• @​aznashwan made their first contribution in uuid-rs/uuid#878

Full Changelog: uuid-rs/uuid@v1.23.0...v1.23.1

Commits

• ca0c85f Merge pull request #879 from uuid-rs/cargo/v1.23.1
• b4db015 prepare for 1.23.1 release
• 771069d Merge pull request #878 from aznashwan/fix-from-gregorian-deprecation-note
• 80994a2 fix: Timestamp::from_gregorian deprecation note
• 90c5be8 Merge pull request #877 from guybedford/remove-wasm-bindgen-msrv
• 8b8c4f4 Remove deprecated feature from wasm-bindgen dependency
• See full diff in compare view

Updates rustls from 0.23.37 to 0.23.40

Commits

• b44c09f Prepare 0.23.40
• e7a555f Prefer Ord::max to core::cmp
• c0005be ech: base inner name padding on actual extension
• 4e49529 ech: test inner name padding
• 3e06ef1 ech: add both name and "gross" padding
• c574ffd ech: avoid short-lived allocation for padding
• 8bf935c ech: pop comment from match arm
• 9088004 ech: expand maximum_name_length to usize ASAP
• a612901 Default require_ems based on CryptoProvider FIPS status
• 0541605 Cargo: version 0.23.38 -> 0.23.39
• Additional commits viewable in compare view

Updates sentry from 0.47.0 to 0.48.0

Release notes

Sourced from sentry's releases.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;
// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
.unit(Unit::Millisecond) // units can also be set on gauges
.attribute("http.status", 200) // attributes can be set on all metric types
.capture();

Fixes

• Fixed several feature additivity SemVer violations, where enabling a feature flag could have introduced breaking changes. All known violations are fixed now, so simply enabling an additional feature flag in any Sentry SDK crate should no longer cause any public API breakages. Fixing these issues required us to break the public API in some places; those breakages are detailed above.

Changelog

Sourced from sentry's changelog.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;
// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
.unit(Unit::Millisecond) // units can also be set on gauges
.attribute("http.status", 200) // attributes can be set on all metric types
.capture();

Fixes

... (truncated)

Commits

• 7f8bb3f release: 0.48.0
• 352cfb8 build(deps): bump actix-http from 3.12.0 to 3.12.1 (#1075)
• 9a1373a build(deps): bump rustls-webpki from 0.103.10 to 0.103.13 (#1085)
• 1bcbbe6 build(deps): bump openssl from 0.10.75 to 0.10.78 (#1078)
• a41084f meta(changelog): Add changelog entries for Metrics PRs
• 3d57614 feat: Metrics feature
• afc5b71 feat(metrics): Add trace_metric transport rate limiting (#1066)
• a68455f feat!(metrics): Add before_send_metric callback (#1064)
• 3c4abb6 feat(metrics): Add metric user attributes from scope (#1063)
• 0e46166 feat(metrics): Attach default SDK attributes to metrics (#1062)
• Additional commits viewable in compare view

Updates sentry-tracing from 0.47.0 to 0.48.0

Release notes

Sourced from sentry-tracing's releases.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;
// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
.unit(Unit::Millisecond) // units can also be set on gauges
.attribute("http.status", 200) // attributes can be set on all metric types
.capture();

Fixes

• Fixed several feature additivity SemVer violations, where enabling a feature flag could have introduced breaking changes. All known violations are fixed now, so simply enabling an additional feature flag in any Sentry SDK crate should no longer cause any public API breakages. Fixing these issues required us to break the public API in some places; those breakages are detailed above.

Changelog

Sourced from sentry-tracing's changelog.

0.48.0

Breaking Changes

• Added the following metrics-related fields to the ClientOptions struct in sentry-core. Both fields are no-ops, unless the metrics feature flag is enabled:
  • enable_metrics, used to enable sending metrics to Sentry (#1073).
  • before_send_metric, used to define a callback for filtering/pre-processing metrics before sending to Sentry (#1064).
• There are several breakages related to the SemVer feature additivity bug fixes:
  • sentry_core::ClientOptions fields before_send_log, enable_logs, auto_session_tracking, and session_mode are no longer gated behind the logs and release-health feature flags (#1091). Code that constructs ClientOptions with a full struct literal (without ..Default::default()), or which exhaustively matches against it, must now include all four fields regardless of enabled features.
  • sentry_core::Scope can no longer be publicly constructed or exhaustively matched against, even when the client feature is disabled (#1094). Previously, both of these were possible when client was disabled.
  • sentry_core::Scope::add_event_processor now requires passed closures to be RefUnwindSafe (#1093). Thanks to this change, sentry_core::Scope is now UnwindSafe regardless of feature flag configuration; previously, Scope was only UnwindSafe when the client feature was disabled.
  • sentry_tracing::EventMapping is now #[non_exhaustive] (#1097).
  • sentry_log::RecordMapping is now #[non_exhaustive] (#1098).

New Features

📊📈💯 The Sentry-Rust SDK now supports emitting Sentry Metrics (#1073)!

To get started, you will need to add the metrics feature flag when compiling the sentry crate. You will also need to enable metrics when initializing the SDK, like so:

use sentry::ClientOptions;
let _guard = sentry::init((
"(your DSN here)",
ClientOptions {
enable_metrics: true,
// ... other options ...
..Default::default()
},
));

You can then capture metrics as follows:

use sentry::metrics;
use sentry::types::protocol::latest::Unit;
// We support counter, gauge, and distribution metrics.
metrics::counter("example.counter", 1).capture();
metrics::gauge("connections", 20).capture();
metrics::distribution("response.time", 123.4)
.unit(Unit::Millisecond) // units can also be set on gauges
.attribute("http.status", 200) // attributes can be set on all metric types
.capture();

Fixes

... (truncated)

Commits

• 7f8bb3f release: 0.48.0
• 352cfb8 build(deps): bump actix-http from 3.12.0 to 3.12.1 (#1075)
• 9a1373a build(deps): bump rustls-webpki from 0.103.10 to 0.103.13 (#1085)
• 1bcbbe6 build(deps): bump openssl from 0.10.75 to 0.10.78 (#1078)
• a41084f meta(changelog): Add changelog entries for Metrics PRs
• 3d57614 feat: Metrics feature
• afc5b71 feat(metrics): Add trace_metric transport rate limiting (#1066)
• a68455f feat!(metrics): Add before_send_metric callback (#1064)
• 3c4abb6 feat(metrics): Add metric user attributes from scope (#1063)
• 0e46166 feat(metrics): Attach default SDK attributes to metrics (#1062)
• Additional commits viewable in compare view

Updates reqwest from 0.13.2 to 0.13.3

Release notes

Sourced from reqwest's releases.

v0.13.3

tl;dr

• Fix CertificateRevocationList parsing of PEM values.
• Fix logging in resolver to only show host, not full URL.
• Fix hickory-dns to fallback to a default if /etc/resolv.conf fails.
• Fix HTTP/3 to handle STOP_SENDING as not an error.
• Fix HTTP/3 pool to remove timed out QUIC connections.
• Fix HTTP/3 connection establishment picking IPv4 and IPv6.
• Upgrade rustls-platform-verifier.
• (wasm) Only use wasm-bindgen on unknown-* targets.

What's Changed

• Update docs.rs Features by @​JamesWiresmith in seanmonstar/reqwest#2961
• fix: fallback to hickory_resolver's default config if reading /etc/resolv.conf fails by @​monosans in seanmonstar/reqwest#2797
• fix: remove timeout con by @​cuiweixie in seanmonstar/reqwest#2967
• http3: handle stop_sending without error by @​anuraaga in seanmonstar/reqwest#2978
• resolve: debug log to change only host by @​lms0806 in seanmonstar/reqwest#2992
• Edit reference link by @​lms0806 in seanmonstar/reqwest#2996
• docs: more accurate about default HTTP2 window sizes by @​seanmonstar in seanmonstar/reqwest#3007
• [HTTP/3] Optimize IPv6 fallback and enforce HTTPS scheme #2911 by @​lyuzichong in seanmonstar/reqwest#3006
• Upgrade rustls-platform-verifier by @​jplatte in seanmonstar/reqwest#3010
• use wasm-bindgen ecosystem only for wasm32-unknown-* target by @​Ludea in seanmonstar/reqwest#3000
• fix rustls crl pem parsing by @​Threated in seanmonstar/reqwest#3013
• docs(retry): include ReqRep in docsrs by @​seanmonstar in seanmonstar/reqwest#3020

New Contributors

• @​JamesWiresmith made their first contribution in seanmonstar/reqwest#2961
• @​monosans made their first contribution in seanmonstar/reqwest#2797
• @​cuiweixie made their first contribution in seanmonstar/reqwest#2967
• @​anuraaga made their first contribution in seanmonstar/reqwest#2978
• @​lms0806 made their first contribution in seanmonstar/reqwest#2992
• @​lyuzichong made their first contribution in seanmonstar/reqwest#3006
• @​Ludea made their first contribution in seanmonstar/reqwest#3000

Full Changelog: seanmonstar/reqwest@v0.13.2...v0.13.3

Changelog

Sourced from reqwest's changelog.

v0.13.3

• Fix CertificateRevocationList parsing of PEM values.
• Fix logging in resolver to only show host, not full URL.
• Fix hickory-dns to fallback to a default if /etc/resolv.conf fails.
• Fix HTTP/3 to handle STOP_SENDING as not an error.
• Fix HTTP/3 pool to remove timed out QUIC connections.
• Fix HTTP/3 connection establishment picking IPv4 and IPv6.
• Upgrade rustls-platform-verifier.
• (wasm) Only use wasm-bindgen on unknown-* targets.

Commits

• a9a88c4 v0.13.3
• f3f6d9d docs(retry): include ReqRep in docsrs (#3020)
• 5f9c231 fix rustls CRL PEM parsing (#3013)
• 11d835d use wasm-bindgen ecosystem only for wasm32-unknown-* target (#3000)
• 1f72916 Upgrade rustls-platform-verifier (#3010)
• 5d5bf35 [HTTP/3] Optimize IPv6 fallback and enforce HTTPS scheme #2911 (#3006)
• 93dc1b2 docs: more accurate about default HTTP2 window sizes (#3007)
• c5e50f0 docs: update outdated link in comments
• b25611f resolve: debug log to change only host (#2992)
• ca1f479 http3: handle stop_sending without error (#2978)
• Additional commits viewable in compare view

Updates redis from 0.27.6 to 1.2.0

Release notes

Sourced from redis's releases.

redis-1.2.0

What's Changed

• feat: support custom TcpSettings on sentinel client by @​hugobpx in redis-rs/redis-rs#2016
• Attempt to Fix CI by @​nihohit in redis-rs/redis-rs#2017
• Add lazy instantiation to the connection manager. by @​nihohit in redis-rs/redis-rs#2022
• Bump async-io from 2.4.0 to 2.6.0 by @​dependabot[bot] in redis-rs/redis-rs#2029
• Bump env_logger from 0.11.8 to 0.11.10 by @​dependabot[bot] in redis-rs/redis-rs#2027
• Bump itoa from 1.0.17 to 1.0.18 by @​dependabot[bot] in redis-rs/redis-rs#2026
• Bump async-trait from 0.1.88 to 0.1.89 by @​dependabot[bot] in redis-rs/redis-rs#2025
• Bump tokio-util from 0.7.17 to 0.7.18 by @​dependabot[bot] in redis-rs/redis-rs#2023
• Add strategies for routing reads to cluster replicas by @​PDXKimani in redis-rs/redis-rs#1985
• Bump anyhow from 1.0.100 to 1.0.102 by @​dependabot[bot] in redis-rs/redis-rs#2024
• README: Add stanza about AI contributions by @​somechris in redis-rs/redis-rs#2033
• Don't compile tokio runtime when using smol by @​cstyles in redis-rs/redis-rs#2036

New Contributors

• @​cstyles made their first contribution in redis-rs/redis-rs#2036

Full Changelog: redis-rs/redis-rs@redis-1.1.0...redis-1.2.0

redis-1.1.0

1.1.0 (2026-03-20)

Changes & Bug fixes

• Reuse host names during topology parsing. (#1995 by @​nihohit)
• Relax trait requirements from ToRedisArgs impls (#2003 by @​nihohit)
• Fix typo in geo.rs (#2007 by @​cheneyni-451)
• Add a per-connection concurrency limiter (#2002 by @​alexcole)
• Separate overall_response_timeout from response_timeout on cluster connections (#2005 by @​alexcole)
• Fix AsyncConnectionConfig::new documentation (#2006 by @​unixo)

CI improvements

• bench/cache: Dedupe RESP3 detection (#1997 by @​somechris)
• ci: Use the bundled JSON module version for Redis >=8 (#1998 by @​somechris)
• ci: Make RESP3 flag effective for JSON module tests (#1996 by @​somechris)
• ci: Clean up trailing whitespace from configs/actions (#1999 by @​somechris)
• ci: Switch Redis 8 to the bundled JSON module (#2004 by @​somechris)
• tests: Drop tls parameter from TestContext::with_modules (#2008 by @​somechris)
• tests: Disable snapshotting when running Redis in tests (#2010 by @​somechris)

redis-1.0.5

Changes & Bug fixes

• Reduce blocking on async cluster connection. (#1967 by @​nihohit)
• Unconditionally try to set READONLY on cluster connections (#1981 by @​PDXKimani)
• Add async transaction support. (#1969 by @​nihohit)
• Introduce modeled NodeAddress type to clusters (#1982 by @​PDXKimani)
• Add support for StreamingCredentialsProvider to Redis cluster client (#1965 by @​alexcole)

... (truncated)

Commits

• 4508a29 Prepare next version (#2038)
• 66aeef4 Don't compile tokio runtime when using smol (#2036)
• 929469b README: Add stanza about AI contributions (#2033)
• 8b9c124 Bump anyhow from 1.0.100 to 1.0.102 (#2024)
• b21b196 Add strategies for routing reads to cluster replicas (#1985)
• ec8d6fc Bump tokio-util from 0.7.17 to 0.7.18 (#2023)
• 124f4a2 Bump async-trait from 0.1.88 to 0.1.89 (#2025)
• a0fdd4c Bump itoa from 1.0.17 to 1.0.18 (#2026)
• 8c4349a Bump env_logger from 0.11.8 to 0.11.10 (#2027)
• f392b28 Bump async-io from 2.4.0 to 2.6.0 (#2029)
• Additional commits viewable in compare view

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

[dependabot]

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