@tanstack/offline-transactions@1.0.56

Patch Changes

• Ignore repeated leadership notifications when the state has not changed to avoid restarting active replay. Settle each transaction's commit when that transaction completes, without waiting for the shared queue to drain. (#1816)

  Keep a completed transaction registered until its outbox deletion settles so a leadership change during deletion does not schedule the same mutation again.

• Preserve fractional top-k replacements regardless of delta order, including left-join updates, and honor B-tree lookup fallbacks after node splits. Preserve own JSON data properties such as __proto__ during mutation detachment and offline transaction serialization. (#1816)

  Compare same-key top-k values directly instead of hashing every replacement. This preserves cyclic payloads and avoids unnecessary full-payload traversal for ordinary updates.

  Cancel structurally equal mapped top-k deltas before applying replacements. Escape Date-marker-shaped user objects in new offline records while retaining read support for the original record format.

  Offline storage compatibility: new records use valueEncoding: 2. Older clients
  cannot decode escaped marker-shaped objects correctly, so do not mix old and
  new clients against the same pending outbox or downgrade while new records
  remain. New clients still read the original unversioned format. Unknown
  encodings and corrupt records are reported through warnings and left in
  storage, not silently discarded; recovery policy is tracked in RFC #1659.

  Reject malformed escaped-object markers rather than inventing empty mutation
  data. Avoid redundant transfer work for zero-width fractional top-k windows
  and avoid descriptor writes for ordinary keys during draft copying.

• Updated dependencies [3c4c35d]:

  • @tanstack/db@0.9.2