chore: version packages

Author: github-actions[bot]

.changeset/bounded-container-value-cache.md

@@ -1,5 +1,32 @@
 # loro-crdt-map
 
+## 1.15.2
+
+### Patch Changes
+
+- fcd039c: Fix wasm memory retention when reading a document container by container
+  (loro-dev/loro#1092).
+
+  Every read through a container handle (`LoroMap.keys()`/`get()`,
+  `LoroList.get()`, `LoroText.toJSON()`, ...) decoded the container's value into
+  an in-memory cache that was pinned for the lifetime of the document — about
+  4 KB per container, released only by `doc.free()`. Walking a large document
+  this way (the pattern loro-mirror's initial state build uses) retained ~4 KB ×
+  containers-ever-read and trapped wasm32 at the 4 GiB limit around one million
+  containers.
+
+  The decoded-value cache is now bounded (2048 entries, second-chance FIFO).
+  Evicted entries are pure caches over the KV store and are re-decoded on the
+  next read, so this only changes memory behavior, not API semantics.
+  `doc.free()` semantics are unchanged.
+
+  Measured on the issue's repro (570-turn document, 188k container handles,
+  release build): the handle walk retains no per-container memory (external
+  memory flat at ~84 MiB vs +641 MiB before) and runs ~10x faster
+  (1.28 s vs 12.5 s) thanks to the smaller working set.
+
+- 8874574: perf: cache `kind()` results on container wrappers. `kind()` returns a constant string per container class; it is now memoized after the first call, so repeated reads (e.g. tree traversal in loro-mirror) no longer cross into WASM or allocate a fresh JS string. This extends the existing `id` cache to `kind()`.
+
 ## 1.15.1
 
 ### Patch Changes

.changeset/wasm-kind-cache.md

@@ -1,6 +1,6 @@
 {
   "name": "loro-crdt-map",
-  "version": "1.15.1",
+  "version": "1.15.2",
   "description": "Source maps for the loro-crdt WebAssembly bundles.",
   "repository": {
     "type": "git",

crates/loro-wasm-map/CHANGELOG.md

@@ -1,5 +1,32 @@
 # Changelog
 
+## 1.15.2
+
+### Patch Changes
+
+- fcd039c: Fix wasm memory retention when reading a document container by container
+  (loro-dev/loro#1092).
+
+  Every read through a container handle (`LoroMap.keys()`/`get()`,
+  `LoroList.get()`, `LoroText.toJSON()`, ...) decoded the container's value into
+  an in-memory cache that was pinned for the lifetime of the document — about
+  4 KB per container, released only by `doc.free()`. Walking a large document
+  this way (the pattern loro-mirror's initial state build uses) retained ~4 KB ×
+  containers-ever-read and trapped wasm32 at the 4 GiB limit around one million
+  containers.
+
+  The decoded-value cache is now bounded (2048 entries, second-chance FIFO).
+  Evicted entries are pure caches over the KV store and are re-decoded on the
+  next read, so this only changes memory behavior, not API semantics.
+  `doc.free()` semantics are unchanged.
+
+  Measured on the issue's repro (570-turn document, 188k container handles,
+  release build): the handle walk retains no per-container memory (external
+  memory flat at ~84 MiB vs +641 MiB before) and runs ~10x faster
+  (1.28 s vs 12.5 s) thanks to the smaller working set.
+
+- 8874574: perf: cache `kind()` results on container wrappers. `kind()` returns a constant string per container class; it is now memoized after the first call, so repeated reads (e.g. tree traversal in loro-mirror) no longer cross into WASM or allocate a fresh JS string. This extends the existing `id` cache to `kind()`.
+
 ## 1.15.1
 
 ### Patch Changes

crates/loro-wasm-map/package.json

@@ -1,6 +1,6 @@
 [package]
 name = "loro-wasm"
-version = "1.15.1"
+version = "1.15.2"
 edition = "2021"
 publish = false
 repository = "https://github.com/loro-dev/loro/"

crates/loro-wasm/CHANGELOG.md

@@ -1,6 +1,6 @@
 {
   "name": "loro-crdt",
-  "version": "1.15.1",
+  "version": "1.15.2",
   "description": "Loro CRDTs is a high-performance CRDT framework that makes your app state synchronized, collaborative and maintainable effortlessly.",
   "keywords": [
     "crdt",