loro-crdt 1.13.7 → 1.13.9

package/CHANGELOG.md

@@ -1,5 +1,51 @@
 # Changelog
 
+## 1.13.9
+
+### Patch Changes
+
+- ddc47ec: Retreat the conservative replay base to the latest single-head critical
+  version of the two versions' combined history instead of the beginning of
+  history. When an import or checkout involves a genuinely concurrent branch,
+  the causal replay now starts at the most recent point that no concurrency
+  crosses (in the sense of Eg-walker's critical versions), skipping the
+  fully-synced common prefix that the old empty-version fallback replayed.
+- ddc47ec: Fix a convergence bug where a movable tree's incrementally maintained state
+  could diverge from a full replay of its own oplog. When newly imported
+  operations were concurrent with part of the receiving peer's multi-head
+  frontier, the diff mode was misclassified as concurrency-free and the tree
+  fast path applied the new moves without adjudicating them against the
+  existing concurrent branch. The classifier now verifies that every entry
+  point of the imported region causally covers the whole current frontier,
+  and otherwise retreats the replay base to the latest critical version so
+  the competing branches are replayed together.
+- ddc47ec: Correct LCA unmatched-branch detection when an explicit dependency already
+  covers the same peer's implicit predecessor. Keep those causally newer imports
+  on the current replay base, and avoid rebuilding unchanged list-like containers
+  when a genuinely concurrent update needs a conservative base containing a large
+  common history.
+
+## 1.13.8
+
+### Patch Changes
+
+- ac1feb6: Reduce peak memory across large snapshot import, `toJSON`, update import, and
+  snapshot export by preserving lazy state, bounding the decompressed SSTable
+  block cache by bytes, and preallocating the snapshot output exactly. Snapshot
+  import now validates every embedded SSTable block checksum before accepting
+  external bytes.
+
+  Full snapshot export no longer walks the alive-container graph: store entries
+  for referenced containers are created when the creating op or imported diff is
+  applied, so a cold export after a large import is a flush plus KV export
+  instead of re-reading every container from compressed blocks. As part of this,
+  full export round-trips imported state bytes faithfully (inconsistent
+  alive-container parent metadata is now rejected by shallow export, which still
+  walks, rather than by full export), and an ensured-but-empty mergeable child is
+  no longer materialized into the KV store by a full export — importers resolve
+  it from its parent map marker. First `toJSON` after import also avoids decoding
+  each lazy container twice.
+
 ## 1.13.7
 
 ### Patch Changes