[dependabot]

Bumps the cargo group with 11 updates in the /rust directory:

Package	From	To
lofty	0.25.4	0.25.5
serde_json	1.0.151	1.0.154
parking_lot	0.12.5	0.13.0
libc	0.2.189	0.2.191
thiserror	2.0.20	2.0.21
log	0.4.34	0.4.35
tokio	1.53.1	1.54.1
smb2	0.27.2	0.39.0
rubato	5.0.0	5.0.1
ringbuf	0.5.2	0.6.0
notify	8.2.0	8.2.1

Updates lofty from 0.25.4 to 0.25.5

Release notes

Sourced from lofty's releases.

0.25.5

What's Changed

• ID3v2: Fix {Work, FlagCompilation, FlagPodcast} conversions by @​Serial-ATA in Serial-ATA/lofty-rs#734
• AIFF: Skip the padding of odd-sized COMT comments by @​DistinctBee in Serial-ATA/lofty-rs#737
• Tag: Extend CompanionTag support by @​Serial-ATA in Serial-ATA/lofty-rs#741
• MP4: Fix panic on write errors by @​Serial-ATA in Serial-ATA/lofty-rs#739
• OGG: Fix writing without page alignment by @​Serial-ATA in Serial-ATA/lofty-rs#744
• TagType: Make files writeable in remove_from_path() by @​Serial-ATA in Serial-ATA/lofty-rs#752
• MP4: Fix handling of extended atoms by @​Serial-ATA in Serial-ATA/lofty-rs#755

New Contributors

• @​DistinctBee made their first contribution in Serial-ATA/lofty-rs#737

Full Changelog: https://github.com/Serial-ATA/lofty-rs/blob/main/CHANGELOG.md#0255---2026-10-25

Changelog

Sourced from lofty's changelog.

[0.25.5] - 2026-10-25

Added

• VorbisComments:
  • Added support for GlobalOptions::preserve_format_specific_items() (PR)
  • Added support for WriteOptions::preferred_padding() (PR)
• ApeTag: Added support for GlobalOptions::preserve_format_specific_items() (PR)
• RiffInfoList: Added support for GlobalOptions::preserve_format_specific_items() (PR)

Fixed

• ID3v2: Fixed write errors from ItemKey::{Work, FlagCompilation, FlagPodcast} conversions (issue) (PR)
• AIFF: Fixed parsing of COMT chunks with padding (issue) (PR)
• MP4:
  • Fixed panics on failed ilst writes (issue) (PR)
  • Fixed deletion of unrelated atoms when writing to files with no existing ilst atom (PR)
  • Fixed parsing of files with extended (64-bit) atoms (issue) (PR)
• OGG: Fixed corruption when writing to files without page-aligned packets (issue) (PR)
• TagType: remove_from_path() no longer opens the file in read-only mode (issue) (PR)

Commits

• 59a3f5a 0.25.5
• c66fade MP4: Fix handling of extended atoms
• e08ec1b examples: Print error sources in tag_reader
• 5e766a6 TagType: Make files writeable in remove_from_path()
• f67d335 OGG: Fix writing without page alignment
• f88b02c MP4: Fix writes to untagged files
• cffcebf MP4: Fix panic on write errors
• 19ea20a Tag: Extend CompanionTag support
• fb554eb AIFF: Skip the padding of odd-sized COMT comments (#737)
• ddb9173 build(deps): update gungraun requirement from 0.19.0 to 0.20.0
• Additional commits viewable in compare view

Updates serde_json from 1.0.151 to 1.0.154

Release notes

Sourced from serde_json's releases.

v1.0.154

• Support preserve_order in no_std builds (#1333, thanks @​razmser)

v1.0.153

• Report invalid UTF-8 at the first bad byte (#1345, thanks @​00200200)

v1.0.152

• Preserve sign of -0 in arbitrary_precision mode (#1346, thanks @​yuxi-liu-wired)
• Fix comparison of large non-integer values with f32::INFINITY (#1347, thanks @​yuxi-liu-wired)

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 parking_lot from 0.12.5 to 0.13.0

Release notes

Sourced from parking_lot's releases.

parking_lot-v0.13.0

• Signficantly improved Mutex and RwLock performance under contention by deferring waking up parked threads until after the lock is released. (#545)
• Added per-acquisition state to lock_api raw locks. RawMutex::Guard replaces GuardMarker; rwlocks have separate SharedGuard, ExclusiveGuard, and UpgradableGuard types. Unlock operations consume this state, while upgrade and downgrade operations return replacement state. Bump and raw condition-variable waits borrow and update the state. Consuming operations must release their acquisition on unwind; borrowing operations must restore ownership and valid state, or abort if restoration fails. (#544)
• Raised the MSRV to Rust 1.95 and upgraded all crates to edition 2024. (#533)
• Removed the hardware-lock-elision feature. (#533)
• Removed automatic eventual fairness. Fair unlocking remains available through the explicit fair-unlock APIs. This removes UnparkResult::be_fair. (#533)
• Removed the no-op lock_api/nightly feature. (#533)
• Removed the legacy lock_api const_new methods and the redundant parking_lot const_* constructor functions; the corresponding new methods can be called in constant contexts. (#533)
• Replaced the recursive read methods on RwLock with a dedicated reader-biased RecursiveRwLock type. The RawRwLockRecursive and RawRwLockRecursiveTimed extension traits have been removed from lock_api. (#533)
• Added Once::new_completed for constructing a Once in the completed state. (#520)
• Added Once::{is_completed, wait, wait_force} and the corresponding OnceState query methods. (#533)
• Made additional lock, timeout, parking, and spin-wait accessors usable in constant contexts. (#533)
• Added into_inner_with_raw to lock_api's Mutex, RwLock, and ReentrantMutex. (#524)
• Added RawCondvar, RawCondvarTimed, and the generic Condvar wrapper to lock_api, and implemented parking_lot::Condvar using them. Custom raw condition variables may allow spurious wakeups; their notification methods must then return false or 0. parking_lot::Condvar still guarantees no spurious wakeups and exact notification counts. (#523) (#533)
• Corrected the Send and Sync bounds of lock guards in lock_api. (#533)
• Made RawMutex::is_locked and RawRwLock::{is_locked, is_locked_exclusive} required methods. (#533)
• Renamed MappedRwLockReadGuard::try_map_or_else to try_map_or_err. (#533)
• Clarified the safety requirements of raw lock implementations, including acquire/release synchronization, moving or dropping a locked raw lock, preserving the original lock mode on a failed upgrade, and stable thread IDs. Acquisitions may unwind without leaving a new acquisition held; consuming guard operations release their acquisition on unwind, while bump and wait operations must restore ownership or abort. (#533) (#544)
• Clarified the aliasing requirements of unsafe raw-access, force-unlock, and guard-construction APIs in lock_api. (#533)
• Guard unlocked and unlocked_fair operations now abort if re-locking panics. Default raw-lock bump implementations also abort if re-locking panics. (#533)
• Guard with_upgraded operations abort if raw upgrading or downgrading panics, preserving continuous lock ownership. (#544)
• Parking-lot operations in parking_lot_core are now guaranteed to never unwind. (#533)
• Documented that parking-lot-based synchronization primitives must not be used

... (truncated)

Changelog

Sourced from parking_lot's changelog.

0.13.0 (parking_lot), 0.10.0 (parking_lot_core), 0.5.0 (lock_api) - 2026-10-21

• Signficantly improved Mutex and RwLock performance under contention by deferring waking up parked threads until after the lock is released. (#545)
• Added per-acquisition state to lock_api raw locks. RawMutex::Guard replaces GuardMarker; rwlocks have separate SharedGuard, ExclusiveGuard, and UpgradableGuard types. Unlock operations consume this state, while upgrade and downgrade operations return replacement state. Bump and raw condition-variable waits borrow and update the state. Consuming operations must release their acquisition on unwind; borrowing operations must restore ownership and valid state, or abort if restoration fails. (#544)
• Raised the MSRV to Rust 1.95 and upgraded all crates to edition 2024. (#533)
• Removed the hardware-lock-elision feature. (#533)
• Removed automatic eventual fairness. Fair unlocking remains available through the explicit fair-unlock APIs. This removes UnparkResult::be_fair. (#533)
• Removed the no-op lock_api/nightly feature. (#533)
• Removed the legacy lock_api const_new methods and the redundant parking_lot const_* constructor functions; the corresponding new methods can be called in constant contexts. (#533)
• Replaced the recursive read methods on RwLock with a dedicated reader-biased RecursiveRwLock type. The RawRwLockRecursive and RawRwLockRecursiveTimed extension traits have been removed from lock_api. (#533)
• Added Once::new_completed for constructing a Once in the completed state. (#520)
• Added Once::{is_completed, wait, wait_force} and the corresponding OnceState query methods. (#533)
• Made additional lock, timeout, parking, and spin-wait accessors usable in constant contexts. (#533)
• Added into_inner_with_raw to lock_api's Mutex, RwLock, and ReentrantMutex. (#524)
• Added RawCondvar, RawCondvarTimed, and the generic Condvar wrapper to lock_api, and implemented parking_lot::Condvar using them. Custom raw condition variables may allow spurious wakeups; their notification methods must then return false or 0. parking_lot::Condvar still guarantees no spurious wakeups and exact notification counts. (#523) (#533)
• Corrected the Send and Sync bounds of lock guards in lock_api. (#533)
• Made RawMutex::is_locked and RawRwLock::{is_locked, is_locked_exclusive} required methods. (#533)
• Renamed MappedRwLockReadGuard::try_map_or_else to try_map_or_err. (#533)
• Clarified the safety requirements of raw lock implementations, including acquire/release synchronization, moving or dropping a locked raw lock, preserving the original lock mode on a failed upgrade, and stable thread IDs. Acquisitions may unwind without leaving a new acquisition held; consuming guard operations release their acquisition on unwind, while bump and wait operations must restore ownership or abort. (#533) (#544)
• Clarified the aliasing requirements of unsafe raw-access, force-unlock, and guard-construction APIs in lock_api. (#533)
• Guard unlocked and unlocked_fair operations now abort if re-locking panics. Default raw-lock bump implementations also abort if re-locking panics. (#533)
• Guard with_upgraded operations abort if raw upgrading or downgrading panics, preserving continuous lock ownership. (#544)
• Parking-lot operations in parking_lot_core are now guaranteed to never unwind. (#533)

... (truncated)

Commits

• 1a5c3dd Update changelog
• ec07063 chore: release
• f369d24 Merge pull request #538 from napi-rs/wasi-threads-parker
• 2f4103f Remove the WASI backend note from stable restrictions
• a3e8717 Reuse existing CI jobs for WASI coverage
• c2bfc7b Merge pull request #549 from Amanieu/fix-l4re-condvar-clock
• 696f28b Don't use pthread_condattr_setclock on L4RE
• 52941c0 Share the libc dependency between Unix and WASI
• 4fde6a7 Align the Rust setup action with existing workflows
• f0ce547 Reuse the pthread backend for WASI on stable
• Additional commits viewable in compare view

Updates libc from 0.2.189 to 0.2.191

Release notes

Sourced from libc's releases.

0.2.191

Support

• Emscripten: Support v4.0.12 to v6.0.11 (#5610)

Added

• Apple: Add F_SETNOSIGPIPE and F_GETNOSIGPIPE (#5609)
• Apple: add ifaliasreq and in6_aliasreq (#5557)
• FreeBSD: Add PT_* constants (#5625)
• Haiku: Add AI_* and NI_* constants from netdb.h (#5585)
• Hurd: Add POSIX_SPAWN_* flags (#5578)
• NuttX: Add AT_SYMLINK_NOFOLLOW (#5614)
• OpenBSD: Add sensordev (#5534)
• QuRT: Add isatty (#5618)
• WASI: Add pthread_condattr_{get,set}clock (#5626)

Fixed

• FreeBSD-aarch64: Fix gpregs and fpregs (#5603)

Changed

• AIX: Restore 'c_ulong' as the type of 'statvfs.f_fsid'. (#5616)
• Android: Make prop_info an extern type (#5561)
• Apple: Mach API is now available on non-MacOS targets again. This should resolve some issues building ecosystem crates. (#5612), (#5636)
• FreeBSD: Add back NOTE_PCTRLMASK with a deprecation warning (#5600)

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"

... (truncated)

Changelog

Sourced from libc's changelog.

0.2.191 - 2026-10-16

Support

• Emscripten: Support v4.0.12 to v6.0.11 (#5610)

Added

• Apple: Add F_SETNOSIGPIPE and F_GETNOSIGPIPE (#5609)
• Apple: add ifaliasreq and in6_aliasreq (#5557)
• FreeBSD: Add PT_* constants (#5625)
• Haiku: Add AI_* and NI_* constants from netdb.h (#5585)
• Hurd: Add POSIX_SPAWN_* flags (#5578)
• NuttX: Add AT_SYMLINK_NOFOLLOW (#5614)
• OpenBSD: Add sensordev (#5534)
• QuRT: Add isatty (#5618)
• WASI: Add pthread_condattr_{get,set}clock (#5626)

Fixed

• FreeBSD-aarch64: Fix gpregs and fpregs (#5603)

Changed

• AIX: Restore 'c_ulong' as the type of 'statvfs.f_fsid'. (#5616)
• Android: Make prop_info an extern type (#5561)
• Apple: Mach API is now available on non-MacOS targets again. This should resolve some issues building ecosystem crates. (#5612), (#5636)
• FreeBSD: Add back NOTE_PCTRLMASK with a deprecation warning (#5600)

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 ...
</tr></table> 

... (truncated)

Commits

• ccc2ff4 libc: Release 0.2.191
• bce6efb apple: Add mach_task_self and mach_task_self_ to semver checks
• ecf4fd4 apple: Re-restrict mach_vm_map to MacOS-only
• b0e0423 Revert "apple: Disable mach.h API on Apple mobile OSs"
• 9c7f568 apple: add ifaliasreq and in6_aliasreq
• 018c7e9 wasi: Add pthread_condattr_{get,set}clock
• 2c77185 openbsd: add sensordev structure
• e10813c hurd: Add missing POSIX_SPAWN_* flags
• 2ea4bc1 Fix FreeBSD/aarch64
• 6d666fd dragonfly: Parse version from headers rather than CLI
• Additional commits viewable in compare view

Updates thiserror from 2.0.20 to 2.0.21

Release notes

Sourced from thiserror's releases.

2.0.21

• Fix parsing of generic unit variants in display expressions (#459)

Commits

• b1827ee Release 2.0.21
• 58037b5 Merge pull request #459 from dtolnay/turbofish
• f82a0cf Keep track of nested turbofish depth
• 72ea492 Raise required compiler to Rust 1.77
• 72eea0d Resolve io_other_error clippy lint in tests
• 07f09a2 Raise required compiler to Rust 1.74
• 2715388 Update ui test suite to nightly-2026-09-22
• 5a306c7 Update ui test suite to nightly-2026-09-05
• ef9383b Update ui test suite to nightly-2026-08-22
• 8336b84 Update ui tests for version 2.0.20
• See full diff in compare view

Updates log from 0.4.34 to 0.4.35

Release notes

Sourced from log's releases.

v0.4.35

This release doesn't include source changes. It verifies log's new CI/CD processes.

Other

• rework CI/CD to align with Rust project standards

Changelog

Sourced from log's changelog.

0.4.35 - 2026-10-30

This release doesn't include source changes. It verifies log's new CI/CD processes.

Other

• rework CI/CD to align with Rust project standards

Commits

• a46450b Update CHANGELOG.md
• a715f17 chore: release v0.4.35
• b4e2b12 Merge pull request #747 from rust-lang/chore/release-plz-mgnt
• 6b490b6 run fmt
• 2c7fd52 simplify some crate release tasks for easier automation
• 5bc5545 Merge pull request #745 from marcoienibot/release-plz-disable-semver-check
• 4234b8c Disable release-plz semver check
• 95918ff Merge pull request #744 from Kobzol/trusted-publishing
• e7ed747 Fix Zizmor lints
• e87a3c6 Setup trusted publishing
• Additional commits viewable in compare view

Updates tokio from 1.53.1 to 1.54.1

Release notes

Sourced from tokio's releases.

Tokio v1.54.1

1.54.1 (October 21st, 2026)

Fixed

• time: revert "remove the runtime handle from timers" (#8692)

#8692: tokio-rs/tokio#8692

Tokio v1.54.0

1.54.0 (October 19th, 2026)

The 1.54.0 release includes all changes up to 1.53.3.

The MSRV is increased to 1.85. (#8514)

Added

• fs: add File::set_times, File::set_modified, and fs::FileTimes (#8504)
• net: implement Default for named_pipe::{ClientOptions, ServerOptions} (#8378)
• runtime: add Builder::max_io_events_per_busy_tick (#8410)
• runtime: stabilize tokio::runtime::worker_index() (#8431)
• sync: add SemaphorePermit::semaphore() (#8482)
• sync: add blocking_acquire methods to Semaphore (#8269)
• sync: add watch::Receiver::is_closed (#8481)
• wasm: support JSPI for Emscripten target (#8285, #8627)
• wasm: support the wasm32-unknown-emscripten target (#8281, #8422, #8528, #8628)

Changed

• fs: reject zero in File::set_max_buf_size (#8449)
• io: make copy_buf cooperative (#8459)
• io: panic when BufReader or BufStream is created with zero capacity (#8494)
• io: panic when in-memory pipe is created with zero capacity (#8397)
• io: reject zero buffer size in copy_bidirectional_with_sizes (#8454)
• io: support vectored writes in Sink (#8663)
• net: start UnixStream::pair and UnixDatagram::pair sockets as writable (#8444)
• net: start accepted sockets as readable and writable (#8435)
• net: support UCred on Fuchsia (#8257)
• process: use mio::unix::pipe for Unix child stdio (#8603)
• runtime: cache-pad the shared injection queue and idle state (#8622)
• runtime: decide auto-boxing of spawned futures at monomorphization time (#8414)
• runtime: make enable_io available whenever rt is enabled (#8387)
• runtime: move block_in_place setup into a non-generic function (#8315)
• runtime: move the multi-thread inject queue to its own mutex (#8382)
• runtime: panic when max_io_events_per_tick is zero (#8476)
• runtime: suggest .await in nested block_on panic message (#8501)
• sync: avoid atomic reader count in broadcast slots (#8357)
• sync: use acquire/release orderings in Notify (#8325)
• time: remove the runtime handle from timers (#8458)

... (truncated)

Commits

• b53b200 chore: prepare Tokio v1.54.1 (#8693)
• 5ed619b time: revert "remove the runtime handle from timers" (#8692)
• 66d34e4 chore: prepare Tokio v1.54.0 (#8667)
• 0d322ce io: support vectored writes in sink (#8663)
• 4167c56 codec: expose I/O sources from codec errors (#8665)
• cdd9dae fs: propagate iouring stress test failures (#8644)
• 52ac781 ci: run the emscripten JSPI tests as an auto-initialized ES module (#8640)
• 4890d02 stream: implement FusedStream for JoinSetStream (#8629)
• a6bd8e1 wasm: check Emscripten version when using JSPI (#8627)
• 9dd749d Merge 'tokio-1.53.3' into 'master' (#8641)
• Additional commits viewable in compare view

Updates smb2 from 0.27.2 to 0.39.0

Changelog

Sourced from smb2's changelog.

[0.39.0] - 2026-10-31

Breaking

• FileNotifyAction has three new variants and is now #[non_exhaustive]: StreamAdded, StreamRemoved, and StreamModified (actions 6-8), which used to fail the whole batch of events as invalid data. An exhaustive match needs a _ arm.

Added

• Named streams, on files and folders, DFS links included (#9): list_streams, read_stream, write_stream, and delete_stream on Tree and SmbClient. A stream name travels apart from its path, so a : in a file name stays a name character. write_stream never creates a missing file, and a stream op works on a file another client has open.
• macOS extended attributes, stored the way macOS's own SMB client stores them: get_xattr, set_xattr, remove_xattr, and list_xattrs. A Finder tag written here reads through a mount byte for byte, and the other way round, proved on a QNAP. com.apple.FinderInfo and com.apple.ResourceFork map onto AFP_AfpInfo and AFP_Resource. get_xattr is Ok(None) when the file has no such attribute and ErrorKind::NotFound when the file is gone. The crate stays byte-level: no plists, no tag model.
• Reading one xattr from many files overlaps on one connection: get_xattr_many and set_xattr_many give results in input order, each independent of the others, and Tree::get_xattr_each hands them over as they finish, so one slow file doesn't hold back a listing. 2,000 files took 1.7 s against a QNAP, 6.3 times the speed of getxattr through a macOS mount over the same route. BatchOptions::assume_paths_exist reads "not found" as "no attribute" for paths you just listed, at one round trip per file.
• Tree::fs_attributes and SmbClient::fs_attributes: whether a share has named streams, its file system's name, and its longest name.
• Tree::watch_with and SmbClient::watch_with: WatchOptions::metadata also reports xattr and stream changes, so another client's tag shows up. watch behaves as before.
• Error::StreamDeleteIgnored: a QNAP answers success to deleting com.apple.metadata:_kMDItemUserTags or AFP_Resource and keeps them, for macOS's own client too. delete_stream and remove_xattr check, and say so with kind ErrorKind::Unsupported. To clear Finder tags, write what macOS writes: a plist holding an empty array.
• Error::NamedStreamsUnsupported: what a stream op answers on a share with no named streams, kind ErrorKind::Unsupported.
• smb-consumer-fruit in the testing feature (port 10495, TestServers::fruit_client): a server with vfs_fruit and named streams. TestServers::start_all now also starts it and smb-consumer-maxreadsize, which it left out.
• smb2-cli 0.6.0: smb2 xattr and smb2 streams. xattr works like macOS's command (-l, -p NAME, -w NAME VALUE, -x, -d NAME), with -j, --from-file, --json, and --dry-run.

Notes

• smb2-cli 0.6.0 also picks up 0.37.0 and 0.38.0, so it now refuses a DFS link to another server.
• Server behavior and every number above: docs/notes/named-streams-and-xattrs.md. No Windows server was tested.

[0.38.0] - 2026-10-31

Security

• A DFS referral can no longer send your credentials to a different server by default. A referral comes from the server, and following one dialed the host it named and signed in there, so a malicious or compromised share could point a link, a namespace root, or an Interlink at a machine of its own and capture the sign-in. A client now follows a referral only to its own server, and answers anything else with the new Error::DfsTargetNotAllowed { path, server, target } (kind ErrorKind::DfsTargetNotAllowed, not retryable) without dialing. Hosts compare after ASCII case, one trailing dot, and an IP's spelling; a short name and its FQDN, or a name and its IP, count as different.

Breaking

• Following a referral to another server now takes ClientConfig::dfs_target_policy. DfsTargetPolicy::SameServerOnly is the default, DfsTargetPolicy::Ask(Arc<dyn Fn(&DfsSignIn) -> bool + Send + Sync>) decides per (server, target) pair and is asked on every use, so taking a consent back stops a link on its next call and a target's automatic reconnect too, and DfsTargetPolicy::FollowAll is the old behavior. A struct literal without ..Default::default() needs the new field.

Notes

• No smb2-cli release goes with this one. The CLI in the repo builds against 0.38.0 with the default policy, so once it's next released it refuses a link to another server. The published smb2-cli 0.5.2 stays on 0.36.2.

[0.37.0] - 2026-10-31

Breaking

• A DFS link whose target can't be reached is no longer ErrorKind::ConnectionLost (#28). It's the new Error::DfsTargetUnreachable { path, target_count, source }, kind ErrorKind::DfsTargetUnreachable (still retryable), because the connection to your share is fine: refuse that one path and keep your session. Before, a consumer reconnecting on ConnectionLost treated one dead link as the whole share gone. If you matched Error::DfsNoReachableTarget from a call through a link or from resolve_dfs_link, match the new variant. A namespace root whose targets are all down stays Error::DfsNoReachableTarget and ConnectionLost, since there the target is the share.

Fixed

• A link's target connection dropping under a call says the same thing. A call on a link's target (followed, or on a DfsLink::tree) that loses that connection returns Error::DfsTargetUnreachable with target_count 1 and the loss as its source. A link on the share's own server, with that connection gone, still reports the lost connection.
• A DFS link's target comes back after it dropped. The client kept the dead connection pooled, so with auto_reconnect off every later call through that link failed until the whole client was rebuilt. The next call now dials the target again.

Notes

... (truncated)

Commits

• 04f3846 Release v0.39.0 — named streams and Finder-compatible macOS xattrs with a pip...
• 39547d3 feat(streams): Finder tags on SMB read and write without a mount, byte-compat...
• 53daaae Release v0.38.0 — a DFS referral can no longer send credentials to a differen...
• 79d0a5b Keep CLI releases building after GitHub retires the macos-14 runner on 2026...
• af304c1 Release v0.37.0 — an unreachable DFS link target is its own error (`Error::Df...
• a23a50e fix(dfs): one dead DFS link no longer looks like a lost connection, so consum...
• 8a7bfc6 Release v0.36.2 — a DFS link resolver (SmbClient::resolve_dfs_link), calls ...
• 7db6ad6 feat(dfs): consumers can ask where a path behind a DFS link lives, calls thro...
• b4a35a2 Release v0.36.1 — a DFS-link download can stream on its own task with the ada...
• bbe3af7 feat(client): DFS-link downloads can stream on their own task with the adapti...
• Additional commits viewable in compare view

Updates rubato from 5.0.0 to 5.0.1

Release notes

Sourced from rubato's releases.

v5.0.1

What's Changed

• Reject a non-finite resample ratio at construction by @​youdie006 in HEnquist/rubato#140
• Handle absurd resample ratios instead of reporting nonsense sizes by @​HEnquist in HEnquist/rubato#141
• Fix startup delay trimming in process_all by @​HEnquist in HEnquist/rubato#143
• Release 5.0.1 by @​HEnquist in HEnquist/rubato#144

New Contributors

• @​youdie006 made their first contribution in HEnquist/rubato#140

Full Changelog: HEnquist/rubato@v5.0.0...v5.0.1

Commits

• eb91908 Merge pull request #144 from HEnquist/release-5.0.1
• c4c81cd Release 5.0.1
• 13889d2 Merge pull request #143 from HEnquist/fix-process-all-trim
• 4d4d104 Trim the startup delay for clips shorter than one chunk
• 601e7ec Move all produced frames when trimming the startup delay
• 1d1da5c Merge pull request #141 from HEnquist/ratio-validation
• f592ccf Check the per-call sizes and the derived ratio too
• 0042c79 Add an unreleased changelog section
• 97accea Handle absurd resample ratios instead of reporting nonsense sizes
• 25a33e3 Merge pull request #140 from youdie006/reject-non-finite-ratio
• Additional commits viewable in compare view

Updates ringbuf from 0.5.2 to 0.6.0

Commits

• See full diff in compare view

Updates notify from 8.2.0 to 8.2.1

Release notes

Sourced from notify's releases.

notify v8.2.1

notify 8.2.1 (2026-10-25)

• CHANGE: raise MSRV from 1.77 to 1.85 #719 #723 breaking
• CHANGE: replace fsevent-sys with objc2-core-foundation and objc2-core-services on macOS, preserving the fsevent-sys feature for compatibility #726
• CHANGE: update windows-sys to 0.61 #1045
• FIX: prevent FsEventWatcher from crashing when unwatching an empty path #718
• FIX: clean up deleted paths in INotifyWatcher even when the kernel has already removed their watch descriptors #720
• FIX: propagate FSEvents stream startup errors from watch, unwatch, and PathsMut::commit #733
• MISC: expand watcher backend tests and fix flaky polling tests #728 #732 #734

#718: notify-rs/notify#718 #719: notify-rs/notify#719 #720: notify-rs/notify#720 #723: notify-rs/notify#723 #726: notify-rs/notify#726 #728: notify-rs/notify#728 #732: notify-rs/notify#732 #733: notify-rs/notify#733 #734: