Skip to content

chore(deps): bump the patch-and-minor group across 1 directory with 10 updates - #32

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/patch-and-minor-5fe92c910b
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/cargo/patch-and-minor-5fe92c910b

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the patch-and-minor group with 10 updates in the / directory:

Package From To
tokio 1.53.1 1.53.2
uuid 1.26.1 1.28.0
zeroize 1.9.0 1.9.1
tokio-util 0.7.19 0.7.20
tokio-rustls 0.26.5 0.26.6
libc 0.2.189 0.2.190
surge-ping 0.9.0 0.9.1
h2 0.4.19 0.4.20
pyo3 0.29.2 0.29.3
eggfetch-core 0.2.0 0.2.2

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 uuid from 1.26.1 to 1.28.0

Release notes

Sourced from uuid's releases.

v1.28.0

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.27.0...v1.28.0

v1.27.0

What's Changed

New Contributors

Full Changelog: uuid-rs/uuid@v1.26.1...v1.27.0

Commits
  • 276c236 Merge pull request #918 from uuid-rs/cargo/v1.28.0
  • 4b3b9f5 prepare for 1.28.0 release
  • cbf9c81 Merge pull request #916 from RanaPriyansh/fix/optional-serde-adapters-840
  • 784a022 Inline expected tokens in optional compact serde test
  • a5678c3 Simplify optional serde adapter tests to option tokens
  • 638a518 Refactor optional serde adapter tests and share byte wrapper
  • b62154e Merge pull request #917 from uuid-rs/cargo/v1.27.0
  • ffd8ec5 prepare for 1.27.0 release
  • 654fa5b Add optional serde format adapters
  • 4b6c10f Merge pull request #915 from uuid-rs/fix/v7-ordering
  • Additional commits viewable in compare view

Updates zeroize from 1.9.0 to 1.9.1

Commits

Updates tokio-util from 0.7.19 to 0.7.20

Commits

Updates tokio-rustls from 0.26.5 to 0.26.6

Release notes

Sourced from tokio-rustls's releases.

0.26.6

0.26.5 added an optimization to batch multiple reads which could swallow some errors. Buffer errors so that they propagate to the caller as soon as the caller next reads from the stream.

What's Changed

Commits
  • 8aebb7c Bump version to 0.26.6
  • 6f8509a Rename buffered_err to error
  • bd0494d Buffer and propagate errors from transport
  • a781340 Add regression test for issue 204
  • 9d0dae6 build(deps): bump rustls from 0.23.44 to 0.23.45
  • 0ad049e build(deps): bump rustls from 0.23.43 to 0.23.44
  • 4f913c7 build(deps): bump rcgen from 0.14.9 to 0.14.10
  • See full diff in compare view

Updates libc from 0.2.189 to 0.2.190

Release notes

Sourced from libc's releases.

0.2.190

There is now a single config for enabling 64-bit time_t: libc_unstable_time64. This can be set unconditionally; it opts in to 64-bit time_t on the following platforms that use 32-bit by default:

  • 32-bit Linux-GNU
  • 32-bit Linux-uClibc
  • 32-bit Linux-musl. Note that setting this flag also enables some other changes that happend in musl v1.2.
  • 32-bit Windows-GNU
  • ESP-IDF (all targets with this environment are 32-bit)

Most other 32-bit platforms are either already using 64-bit time_t, or are considered legacy and will not be gaining support from their upstream maintainers.

You can enable this using RUSTFLAGS:

RUSTFLAGS='--cfg=libc_unstable_time64' cargo ...

Note that there may still be some changes to features gated by this config option, hence "unstable" in its name. In the near future we will rename it to just libc_time64. Until then, please test it out and report any bugs you find!

Support

  • Add initial support for HelenOS (#4355)

Added

We are slowly filling out the Default implementations, to reduce the need for mem::zeroed() in user code:

  • Unix: Implement Default for a number of structs, especially on Apple platforms (#5576)
  • Linux, NetBSD: Give statvfs a Default impl (#5583)
  • Linux: Add Default to a linux/can.rs structs (#5257)

Other additions:

  • Expose the libc_unstable_time64 cfg (#5411)
  • Android, Glibc: Add pthread_gettid_np (#5359)
  • Android: Add RTLD_NEXT (#5323)
  • Android: Add reuseport BPF socket options (#5366)
  • Apple: Add TCP header flags, options and SACK limits (#5358)
  • Apple: Add NET_RT_DUMP2 (#5442)
  • Apple: Add posix_spawn_file_actions_add(f)chdir(_np) (#5558)
  • BSD: Add BPF_WORDALIGN (#5320)
  • BSD: Add lchmod and lchflags where supported (#5400)
  • BSD: Add minherit and related constants (#4849)
  • Docs: Add more links to public headers and manual pages (#5407), (#5485)

... (truncated)

Changelog

Sourced from libc's changelog.

0.2.190 - 2026-10-02

There is now a single config for enabling 64-bit time_t: libc_unstable_time64. This can be set unconditionally; it opts in to 64-bit time_t on the following platforms that use 32-bit by default:

  • 32-bit Linux-GNU
  • 32-bit Linux-uClibc
  • 32-bit Linux-musl. Note that setting this flag also enables some other changes that happend in musl v1.2.
  • 32-bit Windows-GNU
  • ESP-IDF (all targets with this environment are 32-bit)

Most other 32-bit platforms are either already using 64-bit time_t, or are considered legacy and will not be gaining support from their upstream maintainers.

You can enable this using RUSTFLAGS:

RUSTFLAGS='--cfg=libc_unstable_time64' cargo ...

Note that there may still be some changes to features gated by this config option, hence "unstable" in its name. In the near future we will rename it to just libc_time64. Until then, please test it out and report any bugs you find!

Support

  • Add initial support for HelenOS (#4355)

Added

We are slowly filling out the Default implementations, to reduce the need for mem::zeroed() in user code:

  • Unix: Implement Default for a number of structs, especially on Apple platforms (#5576)
  • Linux, NetBSD: Give statvfs a Default impl (#5583)
  • Linux: Add Default to a linux/can.rs structs (#5257)

Other additions:

  • Expose the libc_unstable_time64 cfg (#5411)
  • Android, Glibc: Add pthread_gettid_np (#5359)
  • Android: Add RTLD_NEXT (#5323)
  • Android: Add reuseport BPF socket options (#5366)
  • Apple: Add TCP header flags, options and SACK limits (#5358)
  • Apple: Add NET_RT_DUMP2 (#5442)
  • Apple: Add posix_spawn_file_actions_add(f)chdir(_np) (#5558)
  • BSD: Add BPF_WORDALIGN (#5320)
  • BSD: Add lchmod and lchflags where supported (#5400)
  • BSD: Add minherit and related constants (#4849)

... (truncated)

Commits
  • 7b0ab55 ci: Rename publish_0.2.yml to release.yaml
  • ac85dde ci: Sync release permissions with main
  • 8f8cd20 libc: Release 0.2.190
  • 052c6e6 changelog: Fix an incorrect commit link
  • ea19fd7 test: Remove explicit libc version
  • 6dbf3a2 dragonfly: Move INHERIT_ZERO to the freebsd module
  • 8a64766 apple: add posix_spawn_file_actions_add(f)chdir(_np)
  • 28de514 linux, netbsd: Give statvfs a Default impl
  • a58a95f cygwin: Change POSIX_SPAWN_* flags to c_short
  • d175264 apple: timeval32 is exhaustive
  • Additional commits viewable in compare view

Updates surge-ping from 0.9.0 to 0.9.1

Release notes

Sourced from surge-ping's releases.

v0.9.1

A bug-fix release. No public API was changed or removed.

Five defects broke the "one Client, many concurrent targets" use case that examples/multi_ping.rs is built on, and two more made ICMP error replies undeliverable. The whole test suite passed before these fixes: it covered the code, but not the guarantees.

Fixed

  • Dropping one Client clone broke every other clone. Client::drop marked the shared reply map destroyed unconditionally, so releasing any clone made the survivors fail with ClientDestroyed. The socket, reply map and receiving task now live in one Arc and are torn down only with the last handle — which also removes a race that could leak the receiving task when two clones were dropped concurrently.
  • A duplicate request destroyed the one already in flight. Registering a second waiter for the same (host, identifier, sequence) replaced the first one's sender, so the original ping failed with NetworkError. The existing waiter is now left untouched.
  • A cancelled ping leaked its registration, so that sequence number stayed unusable and the reply map grew without bound.
  • Dropping a Pinger cancelled unrelated requests. Cleanup was keyed by (host, identifier, sequence) alone, so a finished Pinger could unregister whichever request held that key.
  • Requests in flight waited out their timeout when the last Client was dropped, then reported NetworkError. They now return ClientDestroyed immediately.
  • ICMP errors never reached the request waiting for them. Time exceeded, destination unreachable and friends are sent by an intermediate router, but were routed on that router's address instead of the target quoted inside the error, so they surfaced as timeouts. A TTL-limited probe depends on this.
  • The quoted echo header was assumed to be at a fixed offset, so IPv4 header options or IPv6 extension headers shifted the identifier and sequence out from under the parser.
  • The IPv6 identifier and sequence were read 4 bytes early, off the quoted ICMPv6 type, code and checksum.

Added

  • IcmpPacket::real_destination() — the address the request being answered was originally sent to.

Internal

  • Regression tests for each fix. The reply-map, guard and packet-decoding tests open no socket and are fully deterministic.
  • A GitHub Actions workflow: rustfmt, clippy, docs, MSRV 1.85.0, cargo audit, and a build matrix over Linux, macOS and Windows.

Full notes in CHANGELOG.md.

Full Changelog: kolapapa/surge-ping@0.9.0...0.9.1

Changelog

Sourced from surge-ping's changelog.

[0.9.1] - 2026-09-16

A bug-fix release. No public API was changed or removed.

Fixed

  • Dropping one Client clone no longer breaks the others. Client::drop marked the shared reply map destroyed unconditionally, so releasing any clone made every surviving clone fail with ClientDestroyed — the pattern examples/multi_ping.rs is built on. The socket, reply map and receiving task now live in one Arc and are torn down only when the last handle goes. This also removes a race where two clones dropped concurrently could leave the receiving task running.
  • A duplicate request no longer destroys the request already in flight. Registering a second waiter for the same (host, identifier, sequence) replaced the first one's sender, so the original ping failed with NetworkError while the duplicate got IdenticalRequests. The existing waiter is now left untouched.
  • A cancelled ping releases its sequence number. Cancelling the future used to leave the registration behind, leaking memory and making that sequence unusable until the Pinger was dropped.
  • Dropping a Pinger no longer cancels an unrelated request. Cleanup was keyed by (host, identifier, sequence) alone, so a finished Pinger could unregister whichever request held that key at the time, failing it with NetworkError.
  • Requests in flight end as soon as the last Client is dropped. They used to stay parked until their own timeout expired and then report NetworkError; they now return ClientDestroyed immediately.
  • ICMP errors reach the request waiting for them. Time exceeded, destination unreachable and similar errors are sent by an intermediate router, but were routed on that router's address rather than on the target quoted inside the error, so they surfaced as timeouts. This is what a TTL-limited probe depends on.
  • The quoted echo header is located correctly when the original packet carried IPv4 header options or IPv6 extension headers. Its offset was assumed fixed, so the identifier and sequence were read out of the options or the extension headers.
  • The IPv6 identifier and sequence are read from the right offset. They were taken 4 bytes early, off the quoted ICMPv6 type, code and checksum.
  • Icmpv6Packet::get_real_dest is now set for ICMPv6 error messages; it previously kept its ::1 default.

Added

  • IcmpPacket::real_destination() — the address the request being answered was originally sent to. For an echo reply this is the sender; for an ICMP error it is read out of the request quoted inside the error.

Internal

... (truncated)

Commits
  • 641dda8 test: stop assuming the platform keeps the identifier hint
  • 8da7bd7 chore(release): bump version to 0.9.1
  • 3b2d6fb ci: add GitHub Actions workflow
  • 3c7e92b fix: correct concurrency and ICMP error routing defects
  • ba11a19 style: apply rustfmt and fix clippy warnings
  • 17a0873 docs: rewrite README and add architecture diagram
  • See full diff in compare view

Updates h2 from 0.4.19 to 0.4.20

Release notes

Sourced from h2's releases.

v0.4.20

What's Changed

New Contributors

Full Changelog: hyperium/h2@v0.4.19...v0.4.20

Changelog

Sourced from h2's changelog.

0.4.20 (October 6, 2026)

  • Fix counting reserved push promises against stream concurrency limits.
  • Fix automatic small DATA frame budget to update when the connection window changes at runtime.
  • Fix rejecting duplicate content-length headers with different values.
  • Fix counting refused streams towards the local reset limit.
  • Fix client to reject responses without a :status pseudo header.
  • Fix rare race condition during shutdown.
  • Fix rejecting GOAWAY frames with a non-zero stream identifier.
  • Optimize HPACK Huffman encoding and decoding.
  • Reduce size of HPACK Huffman encoding tables.
  • Optimize receive performance by reducing send buffer locking.
Commits
  • b0e8908 v0.4.20
  • 5b17a0e perf: remove need to lock for pending_refusal for every recv call (#969)
  • a26b427 fix: count reserved push promises against stream concurrency (#968)
  • 96c15eb fix: update automatic DATA frame budget at runtime (#965)
  • d96d347 fix: reject duplicate content-lengths that differ (#967)
  • 8e9655f fix: count refused streams on local reset abuse counter (#966)
  • 3c5f61c fix(client): reject responses without :status (#959)
  • e43124b fix: rare race during shutdown (#956)
  • 20cfc37 style: apply clippy (#955)
  • d785c5f chore: make CI have a single required job (#954)
  • Additional commits viewable in compare view

Updates pyo3 from 0.29.2 to 0.29.3

Release notes

Sourced from pyo3's releases.

PyO3 0.29.3

This release is a series of fixes worth landing to the PyO3 0.29 series; the PyO3 0.30 release is planned to follow within a few weeks, however during the development cycle a number of rough edges were discovered which were deemed worth a backport.

The patch broadly includes:

  • a further fix the to the opt-out of raw-dylib linking for Windows introduced in PyO3 0.29.1 (the switch to raw-dylib linking was introduced in PyO3 0.29.0),
  • fixes to support GraalPy on windows,
  • a handful of small performance optimizations,
  • a number of non-breaking fixes to the experimental-inspect type stub generation (expect more improvements in 0.30), and
  • various other bugfixes such as to FFI definitions, to resolve crashes, and to fix clippy lints caused by PyO3 macros.

For a full list of the exact fixes please consult the CHANGELOG.

Thank you to the following contributors for the improvements:

@​adamgerhant-ai @​alex @​bschoenmaeckers @​charliermarsh @​chirizxc @​davidhewitt @​dependabot[bot] @​dylanpulver @​exg @​FranciscoTGouveia @​JMak-Security @​jonasdedden @​jorenham @​konstin @​latent-9 @​mejrs @​ngoldbaum @​Person-93 @​PeterFaiman @​sneakers-the-rat

Changelog

Sourced from pyo3's changelog.

[0.29.3] - 2026-09-30

Packaging

  • Support GraalPy on Windows. #6406

Added

  • Add FFI definitions PyModule_GetState_DuringGC, PyModule_GetToken_DuringGC, PyObject_GetTypeData_DuringGC, PyType_GetModuleState_DuringGC, PyType_GetBaseByToken_DuringGC, PyType_GetModule_DuringGC, and PyType_GetModuleByToken_DuringGC for Python 3.15 and up. #6419

Changed

  • Optimize u128/i128 conversions on Python 3.15+. #6160
  • Preallocate output sets when extracting Python set and frozenset values into Rust hash sets. #6225
  • Optimize PyBytes::as_bytes() when not using abi3 or abi3t. #6377

Removed

  • Remove FFI definitions PyExc_RecursionErrorInst and Py_UseClassExceptionsFlag (not present in supported Python versions). #6421

Fixed

  • Revert removal of FFI definition _PyFrameEvalFunction, _PyInterpreterState_GetEvalFrameFunc and _PyInterpreterState_SetEvalFrameFunc, which are not currently treated as CPython private API despite their name. #6195
  • Fix FFI definition PyUnstable_Eval_RequestCodeExtraIndex FFI binding to link to the private CPython symbol on Python versions before 3.12. #6195
  • Fix FFI definitions PyByteArray_GET_SIZE, PyList_GET_SIZE, and PySet_GET_SIZE to use an atomic load for free-threaded Python. #6230
  • experimental-inspect: deduplicate repeated members of a type union in the generated stubs, and put a space on both sides of the | rather than only before it. #6273
  • experimental-inspect: __next__ and __anext__ returning Option<T> (or PyResult<Option<T>>) are now introspected as returning T, since None stops the iteration instead of being yielded. #6274
  • Fix clippy::clone_on_copy warnings triggered on nightly Rust by #[pyclass(from_py_object)] on classes which implement Copy. #6309
  • experimental-inspect: __pow__, __rpow__ and __get__ now introspect their trailing argument as defaulting to None, matching the CPython slot wrappers which substitute None when it is omitted. #6363
  • experimental-inspect: fix the stubs of a package nested inside another package being written into a directory named after its parent instead of its own name. #6365
  • Fix many unresolved symbols when linking for PyPy due to incorrect link names in pyo3-ffi. #6389
  • Fix empty tuple type hints being rendered as invalid tuple[] instead of tuple[()] in generated stubs and PyStaticExpr display. #6393
  • experimental-inspect: escape stub docstrings to prevent invalid Python syntax. #6394
  • experimental-inspect: fix the generated type annotation for PyBuffer on python <3.12 by using typing_extensions.Buffer instead of collections.abc.Buffer. #6395
  • Fix string constants containing control characters rendering as invalid Python in Display for PyStaticExpr. #6397
  • Fix crash when a detached thread is terminated while trying to reattach during interpreter finalization. #6404
  • Fix link failures on 32-bit Windows when raw-dylib linking is disabled. #6410
  • Fix DLL load failures on Windows with PyPy when raw-dylib linking is disabled. #6410
  • Fix FFI definition PyVectorcall_Call failing to link on Python 3.11 and older. #6410
  • Fix many unresolved data symbols when linking for PyPy due to incorrect link names in pyo3-ffi. #6421
  • Fix linker errors on PyPy for outdated FFI definitions where PyPy moved from a function to a macro. #6422
  • Fix crash when GC traverses a #[pyclass] type object during class attribute initialization. #6453
Commits

Updates eggfetch-core from 0.2.0 to 0.2.2

Release notes

Sourced from eggfetch-core's releases.

v0.2.2

EggFetch v0.2.2

EggFetch 0.2.2 publishes the M007 native transport failure classifier as the coordinated release. It is a patch release under the pre-1.0 compatibility policy: public Rust, Python, C, CLI, and HTTPX APIs, the feature graph and defaults, Rust MSRV (1.89), and dependency policy are unchanged apart from the additive Rust error-domain API below.

Added

  • eggfetch-core: native transport failure classification. Error gains one additive method, transport_failure_kind(), returning Option<TransportFailureKind> for the new #[non_exhaustive] enum TransportFailureKind::{Connect, Tls, Protocol, Cancelled}; None means the typed evidence does not prove a category.

    use eggfetch_core::error::{Error, TransportFailureKind};
    match err.transport_failure_kind() {
    Some(TransportFailureKind::Tls) => { /* TLS config/handshake/verification / }
    Some(TransportFailureKind::Connect) => { / connection establishment / }
    Some(TransportFailureKind::Protocol) => { / HTTP framing / premature body / }
    Some(TransportFailureKind::Cancelled) => { / cancelled before completion / }
    _ => { / unknown, or a future variant */ }
    }

    This is a Rust core surface only. The Python, CLI, FFI, and Node adapters did not gain an equivalent classifier API; use the existing per-adapter error surfaces there.

    The Error enum itself is unchanged — no new variants, no #[non_exhaustive], unchanged kind() tokens and Display. The classifier is diagnostic only and does not imply retryability: RetryPolicy::is_error_retryable() is unchanged and never consults it.

Fixed

Correctness and security hardening from the internal audit that landed after 0.2.1, plus one build fix found by the release gate itself:

  • Core — timeout arithmetic saturates instead of panicking on huge finite values; CONNECT target formatting rejects /, ?, #, and @ in the authority; low-level transport retry is limited to connect-level failures plus stale-pool cancellations; proxy configuration fails closed on a missing host; an empty CA directory fails closed for the ca_certificate (replace) variant; SOCKS deadline overflow is treated as an already-expired Total timeout; Content-Length conflicts are rejected; cross-origin Referer/Origin stripping, proxy-auth conflict handling, redirect SNI/pinning retention, and Total-wins-tie deadline breaking are enforced.
  • Redaction — proxy_rejection_body redacts credential-looking text on token boundaries, the redact helper always truncates at ?/#, TransportHints Debug logs target length only, and the HTTPX cookie __repr__ redacts values.
  • Python — ssl.SSLContext translation rejects security-semantic OP_UNSAFE_LEGACY_RENEGOTIATION, OP_LEGACY_SERVER_CONNECT, OP_NO_TICKET, and OP_NO_RENEGOTIATION; websocket failures raised by native eggfetch errors are translated to WebSocketNetworkError; async streaming iterators spawn on the client runtime handle like sync iterators; non-coroutine async trace callbacks are rejected with TypeError before dispatch.
  • CLI — --no-follow now parses (overrides_with instead of conflicts_with); JSON and NDJSON redirect URLs are routed through safe_url_for_display so userinfo, query, and fragment are stripped.
  • FFI — out-pointers are nulled on allocation failure, the tracking pointer is cleared before Box::from_raw so a panic fallback cannot double-free, the builder is restored on Err, and the bounded C-string scan no longer uses the signed-only cast_unsigned() conversion that made eggfetch-ffi fail to compile on targets where c_char is u8 (aarch64 Linux and other unsigned-c_char targets).
  • Node — header and body FFI failures propagate as napi::Error instead of a silent skip or empty body.

Packages

The PyPI release contains 18 wheels for CPython 3.10–3.15 across Linux x86_64, macOS arm64, and Windows x86_64, plus one source distribution. Python 3.15 has no stable interpreter yet, so the 3.15 wheels were built against CPython 3.15.0-rc.2 on all three platforms; that matrix row will resolve a stable 3.15.x automatically once 3.15.0 final ships.

Verification

... (truncated)

Changelog

Sourced from eggfetch-core's changelog.

[0.2.2] - 2026-10-02

Added

  • eggfetch-core: native transport failure classification. Error gains one additive method, transport_failure_kind(), returning Option<TransportFailureKind> with the new #[non_exhaustive] enum TransportFailureKind::{Connect, Tls, Protocol, Cancelled} (None when the typed evidence does not prove a category). The classifier walks the source()/get_ref() chain with TLS-before-connect precedence and treats a premature-body/malformed-framing io::Error observed at the NativeResponseBody polling boundary as Protocol. It is diagnostic only: Error itself is unchanged (no new variants, no #[non_exhaustive], unchanged kind() tokens and Display), and RetryPolicy::is_error_retryable() never consults it. This is a Rust-core surface only — the Python, CLI, FFI, and Node adapters do not gain an equivalent classifier API.

Fixed

  • Correctness and hardening fixes from the internal audit that landed after 0.2.1, all verified by the qualified Tier 1/Tier 2 gates on this candidate:
    • Core: timeout arithmetic saturates instead of panicking on huge finite values (Duration::MAX-scale totals, started + total overflow); CONNECT target formatting rejects /, ?, #, and @ in the authority; low-level transport retry is limited to connect-level failures plus stale-pool cancellations, ...

      Description has been truncated

…0 updates

Bumps the patch-and-minor group with 10 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [tokio](https://github.com/tokio-rs/tokio) | `1.53.1` | `1.53.2` |
| [uuid](https://github.com/uuid-rs/uuid) | `1.26.1` | `1.28.0` |
| [zeroize](https://github.com/RustCrypto/utils) | `1.9.0` | `1.9.1` |
| [tokio-util](https://github.com/tokio-rs/tokio) | `0.7.19` | `0.7.20` |
| [tokio-rustls](https://github.com/rustls/tokio-rustls) | `0.26.5` | `0.26.6` |
| [libc](https://github.com/rust-lang/libc) | `0.2.189` | `0.2.190` |
| [surge-ping](https://github.com/kolapapa/surge-ping) | `0.9.0` | `0.9.1` |
| [h2](https://github.com/hyperium/h2) | `0.4.19` | `0.4.20` |
| [pyo3](https://github.com/pyo3/pyo3) | `0.29.2` | `0.29.3` |
| [eggfetch-core](https://github.com/eggstack/eggfetch) | `0.2.0` | `0.2.2` |



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 `uuid` from 1.26.1 to 1.28.0
- [Release notes](https://github.com/uuid-rs/uuid/releases)
- [Commits](uuid-rs/uuid@v1.26.1...v1.28.0)

Updates `zeroize` from 1.9.0 to 1.9.1
- [Commits](RustCrypto/utils@zeroize-v1.9.0...zeroize-v1.9.1)

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 `tokio-rustls` from 0.26.5 to 0.26.6
- [Release notes](https://github.com/rustls/tokio-rustls/releases)
- [Commits](rustls/tokio-rustls@v/0.26.5...v/0.26.6)

Updates `libc` from 0.2.189 to 0.2.190
- [Release notes](https://github.com/rust-lang/libc/releases)
- [Changelog](https://github.com/rust-lang/libc/blob/0.2.190/CHANGELOG.md)
- [Commits](rust-lang/libc@0.2.189...0.2.190)

Updates `surge-ping` from 0.9.0 to 0.9.1
- [Release notes](https://github.com/kolapapa/surge-ping/releases)
- [Changelog](https://github.com/kolapapa/surge-ping/blob/main/CHANGELOG.md)
- [Commits](kolapapa/surge-ping@0.9.0...0.9.1)

Updates `h2` from 0.4.19 to 0.4.20
- [Release notes](https://github.com/hyperium/h2/releases)
- [Changelog](https://github.com/hyperium/h2/blob/master/CHANGELOG.md)
- [Commits](hyperium/h2@v0.4.19...v0.4.20)

Updates `pyo3` from 0.29.2 to 0.29.3
- [Release notes](https://github.com/pyo3/pyo3/releases)
- [Changelog](https://github.com/PyO3/pyo3/blob/main/CHANGELOG.md)
- [Commits](PyO3/pyo3@v0.29.2...v0.29.3)

Updates `eggfetch-core` from 0.2.0 to 0.2.2
- [Release notes](https://github.com/eggstack/eggfetch/releases)
- [Changelog](https://github.com/eggstack/eggfetch/blob/main/CHANGELOG.md)
- [Commits](eggstack/eggfetch@v0.2.0...v0.2.2)

---
updated-dependencies:
- dependency-name: tokio
  dependency-version: 1.53.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
- dependency-name: uuid
  dependency-version: 1.28.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: patch-and-minor
- dependency-name: zeroize
  dependency-version: 1.9.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
- dependency-name: tokio-util
  dependency-version: 0.7.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
- dependency-name: tokio-rustls
  dependency-version: 0.26.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
- dependency-name: libc
  dependency-version: 0.2.190
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
- dependency-name: surge-ping
  dependency-version: 0.9.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
- dependency-name: h2
  dependency-version: 0.4.20
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
- dependency-name: pyo3
  dependency-version: 0.29.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
- dependency-name: eggfetch-core
  dependency-version: 0.2.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: patch-and-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 13, 2026
@dependabot @github

dependabot Bot commented on behalf of github Oct 13, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: supply-chain. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@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/patch-and-minor-5fe92c910b branch October 19, 2026 14:44
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants