Sourced from async-trait's releases.
0.1.92
- Resolve double_must_use clippy lint in generated code (#303)
Sourced from log's releases.
0.4.34
What's Changed
- doc: Add context-logger utility to README by
@alekseysidorovin rust-lang/log#735- Add alloc support for boxed loggers by
@malezjaain rust-lang/log#737New Contributors
@alekseysidorovmade their first contribution in rust-lang/log#735@malezjaamade their first contribution in rust-lang/log#737Full Changelog: https://github.com/rust-lang/log/compare/0.4.33...0.4.34
Sourced from log's changelog.
[0.4.34] - 2026-08-22
What's Changed
- doc: Add context-logger utility to README by
@alekseysidorovin rust-lang/log#735- Add alloc support for boxed loggers by
@malezjaain rust-lang/log#737New Contributors
@alekseysidorovmade their first contribution in rust-lang/log#735@malezjaamade their first contribution in rust-lang/log#737Full Changelog: https://github.com/rust-lang/log/compare/0.4.33...0.4.34
Sourced from moka's releases.
v0.12.16
Version 0.12.16
Fixed
- Fixed a bug where cache eviction could stall permanently when the cache was configured with the non-default LRU eviction policy (
EvictionPolicy::lru()) by a race between insert and remove operations on the same key (#592gh-pull-0592 by@kim-jhyeon, reported in #590gh-issue-0590):
- This bug was introduced in v0.12.0 and affected
sync::Cache,sync::SegmentedCacheandfuture::Cache.- A race between applying a write recording for an entry and concurrently removing that entry from the internal concurrent hash table could leave an orphaned node at the front of the LRU queue. Once present, no entry was ever evicted again and the cache grew unboundedly past
max_capacity.- The same race also affected the default TinyLFU eviction policy, but with a milder symptom: each occurrence permanently leaked one phantom entry slot, causing
entry_countandweighted_sizeto over-report and the usable capacity to shrink by one entry per occurrence. Fixed by the same change.Changed
- Worked around a ThreadSanitizer false positive (#602gh-pull-0602):
- Replaced the standalone
fence(Acquire)in the internalMiniArc's drop path with anAcquireload of the reference count, so that downstream projects can now run ThreadSanitizer on code using Moka without hitting this false positive.std::sync::Archas a similar workaround.- Raised the minimum version of the
crossbeam-epochcrate fromv0.9.18tov0.9.20to avoid the following advisory (#603gh-pull-0603):
- [RUSTSEC-2026-0204] crossbeam-epoch: invalid pointer dereference in
fmt::PointerforAtomicandShared- Moka is not affected by this advisory because it never formats these pointer types. However, raising the minimum version prevents downstream lockfiles from resolving to an affected
crossbeam-epochversion via Moka.
Sourced from moka's changelog.
Version 0.12.16
Fixed
- Fixed a bug where cache eviction could stall permanently when the cache was configured with the non-default LRU eviction policy (
EvictionPolicy::lru()) by a race between insert and remove operations on the same key (#592[gh-pull-0592] by [@kim-jhyeon][gh-kim-jhyeon], reported in #590[gh-issue-0590]):
- This bug was introduced in v0.12.0 and affected
sync::Cache,sync::SegmentedCacheandfuture::Cache.- A race between applying a write recording for an entry and concurrently removing that entry from the internal concurrent hash table could leave an orphaned node at the front of the LRU queue. Once present, no entry was ever evicted again and the cache grew unboundedly past
max_capacity.- The same race also affected the default TinyLFU eviction policy, but with a milder symptom: each occurrence permanently leaked one phantom entry slot, causing
entry_countandweighted_sizeto over-report and the usable capacity to shrink by one entry per occurrence. Fixed by the same change.Changed
- Worked around a ThreadSanitizer false positive (#602[gh-pull-0602]):
- Replaced the standalone
fence(Acquire)in the internalMiniArc's drop path with anAcquireload of the reference count, so that downstream projects can now run ThreadSanitizer on code using Moka without hitting this false positive.std::sync::Archas a similar workaround.- Raised the minimum version of the
crossbeam-epochcrate fromv0.9.18tov0.9.20to avoid the following advisory (#603[gh-pull-0603]):
- [RUSTSEC-2026-0204] crossbeam-epoch: invalid pointer dereference in
fmt::PointerforAtomicandShared- Moka is not affected by this advisory because it never formats these pointer types. However, raising the minimum version prevents downstream lockfiles from resolving to an affected
crossbeam-epochversion via Moka.
a616ec1
Merge pull request #604 from
moka-rs/chore/bump-v0.12.163b140a6
Bump the version to v0.12.1651b802d
Merge pull request #603 from
moka-rs/bump-crossbeam-epoch-floor4f90716
Raise the minimum crossbeam-epoch version to 0.9.2008d0e04
Merge pull request #602 from
moka-rs/gh600-tsan-workaround14447a7
Restructure the v0.12.16 TSan workaround CHANGELOG entry7b14c37
Avoid a TSan false positive by replacing the fence in MiniArc::drop05b37c6
Merge pull request #599 from
moka-rs/gh590-deterministic-testsfc31858
Replace private doc references in gh590 test comments5743592
Improve the v0.12.16 CHANGELOG entrySourced from uuid's releases.
v1.26.0
What's Changed
- Add ContextV7::with_additional_precision_bits by
@ChrisJr404in uuid-rs/uuid#904- Prepare for 1.26.0 release by
@KodrAusin uuid-rs/uuid#905Full Changelog: https://github.com/uuid-rs/uuid/compare/1.25.0...v1.26.0
1.25.0
What's Changed
- Add a serde::bytes module that encodes a Uuid as a byte string by
@ChrisJr404in uuid-rs/uuid#902- Prepare for 1.25.0 release by
@KodrAusin uuid-rs/uuid#903New Contributors
@ChrisJr404made their first contribution in uuid-rs/uuid#902Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.24.1...1.25.0
v1.24.1
What's Changed
- Fix non-ASCII character handling in parse diagnostics by
@questfeverin uuid-rs/uuid#899- Prepare for 1.24.1 release by
@KodrAusin uuid-rs/uuid#900New Contributors
@questfevermade their first contribution in uuid-rs/uuid#899Full Changelog: https://github.com/uuid-rs/uuid/compare/v1.24.0...v1.24.1
cdc96a8
Merge pull request #905 from
uuid-rs/cargo/v1.26.034e4f49
don't test macros under mirid9e7242
update nightly used for miriec16819
prepare for 1.26.0 release162cd20
Merge pull request #904 from
ChrisJr404/v7-additional-precision-bits97eceff
Add ContextV7::with_additional_precision_bits for microsecond
clocks302e0bf
Merge pull request #903 from
uuid-rs/cargo/1.25.0b7ccde8
prepare for 1.25.0 releasec62dffb
Merge pull request #902 from
ChrisJr404/serde-bytes-module8c198b2
Add a serde::bytes module that encodes as a byte stringSourced from serde_with's releases.
serde_with v3.22.0
Added
- Add support for
jiffv0.2 behind the newjiff_0_2feature flag (#936)jiff::SignedDurationworks withDurationSecondsand its variants.jiff::Timestamp,jiff::Zoned, andjiff::civil::DateTimework withTimestampSecondsand its variants. Deserializing ajiff::Zoneduses the system time zone, likechrono::DateTime<Local>.Fixed
- Extend the GHSA-7gcf-g7xr-8hxj fix to the duplicate-key-prevention collections. The
rust::sets_duplicate_value_is_error,rust::maps_duplicate_key_is_error,rust::sets_last_value_wins, andrust::maps_first_key_winsadapters created their backing sets/maps withwith_capacity_and_hasherusing the raw deserializersize_hint, bypassing thesize_hint_cautiouscap added in #966 (theclippy.tomldisallowed_methodslint only coversVec::with_capacity, notwith_capacity_and_hasher, so these sites were not flagged). Attacker-controlled input claiming a huge length could panic withHash table capacity overflowbefore a single element was read. All such constructions now route throughsize_hint_cautious.
88f576a
Bump version to 3.22.0 (#991)931e664
Bump version to 3.22.0e26930e
Bump github/codeql-action from 4.37.3 to 4.37.4 in the github-actions
group (...92cd5a0
Bump github/codeql-action in the github-actions group32be66f
Guard with_capacity_and_hasher against untrusted size_hint (DoS) (#971)33871cd
Merge branch 'master' into
fix/duplicate-key-impls-capacity-overflowbb1e064
Change function position within impl (#968)202d3dd
Improve the time unit macros to remove unnecessary repetition and make
the co...b347efb
Move the use_duration_signed_ser/*_de macros
utils6590545
chrono_0_4: Implement the same time unit macro cleanup as jiff_0_2Sourced from roaring's releases.
v0.11.5
What's Changed
- Implement std Error for IntegerTooSmall by
@Kerollmopsin RoaringBitmap/roaring-rs#362- fix: invalid treemap iter advance by
@silver-ymzin RoaringBitmap/roaring-rs#360- Fix off-by-one that corrupts a bitmap in remove_smallest/remove_biggest (#359) by
@youdie006in RoaringBitmap/roaring-rs#363- Upgrade dependencies bump version by
@Kerollmopsin RoaringBitmap/roaring-rs#364New Contributors
@silver-ymzmade their first contribution in RoaringBitmap/roaring-rs#360@youdie006made their first contribution in RoaringBitmap/roaring-rs#363Full Changelog: https://github.com/RoaringBitmap/roaring-rs/compare/v0.11.4...v0.11.5
0ce3fc8
Merge pull request #364
from RoaringBitmap/upgrade-dependencies-bump-versiona961a04
Remove the once_cell dependency5e8445b
Merge pull request #363
from youdie006/fix/359-interval-remove-boundarybf2961d
Bump version to v0.11.5048a8b0
Fix off-by-one that corrupts a bitmap in
remove_smallest/remove_biggest27d84f5
Merge pull request #360
from silver-ymz/fix/treemap-iter-advance-across-bitmapsaac2de8
Make clippy happya3d1d54
Merge pull request #362
from RoaringBitmap/std-error-for-integer-too-small9a3c33e
Implement std Error for IntegerTooSmallf46c0ff
fix: invalid treemap iter advanceSourced from napi's releases.
napi-v3.12.0
Added
- (cli) support non-threaded WASI targets (#3353)
58bd87f
chore: release (#3414)9da8723
chore(release): publish8d22196
chore(deps): update dependency oxc-parser to ^0.142.0 (#3422)abc30fb
build(deps): bump postcss from 8.5.17 to 8.5.23 (#3421)5542139
build(deps): bump fast-xml-parser from 5.9.3 to 5.10.1 (#3418)dc4ee8c
build(deps): bump fast-uri from 3.1.3 to 3.1.4 (#3419)050d985
feat(async-runtime): drain-linger surface + lock-free scheduler
internals (#3...e0b8708
chore(deps): update dependency oxc-parser to ^0.141.0 (#3417)fc84940
chore(deps): update actions/setup-node action to v7 (#3413)ee598db
build(deps): bump protobufjs from 7.6.4 to 7.6.5 (#3410)Sourced from napi-derive's releases.
napi-derive-v3.6.3
Other
- updated the following local packages: napi-derive-backend
napi-derive-v3.6.2
Other
- updated the following local packages: napi-derive-backend
956e452
chore: release (#3448)73048f5
chore(release): publish61fae8a
fix(napi): stop unloading addons with live native code, preserve
non-Error re...93e86ce
chore(release): publish2c90599
fix(cli): support npm 12 pack output (#3449)360b1ec
fix(wasi): avoid randomness during module registration (#3447)b648c40
build(deps): bump nanoid from 3.3.16 to 3.3.18 (#3446)ffda4ef
chore(deps): update dependency js-yaml to v4.3.1 [security] (#3445)387b0dc
feat(cli): size WASI browser worker pools from
navigator.hardwareConcurrency ...61e4346
build(deps): bump fast-uri from 3.1.4 to 3.1.5 (#3440)Sourced from napi-build's releases.
napi-build-v2.4.1
Fixed
- (napi) stop unloading addons with live native code, preserve non-Error rejections, and add the wasm teardown barrier (#3423)
956e452
chore: release (#3448)73048f5
chore(release): publish61fae8a
fix(napi): stop unloading addons with live native code, preserve
non-Error re...93e86ce
chore(release): publish2c90599
fix(cli): support npm 12 pack output (#3449)360b1ec
fix(wasi): avoid randomness during module registration (#3447)b648c40
build(deps): bump nanoid from 3.3.16 to 3.3.18 (#3446)ffda4ef
chore(deps): update dependency js-yaml to v4.3.1 [security] (#3445)387b0dc
feat(cli): size WASI browser worker pools from
navigator.hardwareConcurrency ...61e4346
build(deps): bump fast-uri from 3.1.4 to 3.1.5 (#3440)