[dependabot]

Bumps 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

[davidfestal]

@dependabot rebase

[davidfestal]

@dependabot rebase