Skip to content

chore: version packages - #1099

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: version packages#1099
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 8, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

loro-crdt@1.16.1

Patch Changes

  • d9ddfba: Make repeated concurrent imports fast: retreat the replay base to the latest
    multi-head critical version instead of the single-head one (which is stuck at
    the initial fork point on criss-cross sync DAGs), and let the text/list diff
    calculators trust a certified-critical base instead of rebuilding their
    trackers from the whole history on every concurrent import.

  • 80a0e88: Make imports that are concurrent with the current version only on map/counter
    containers as fast as ordinary linear imports.

    Previously any concurrency between the new ops and the current version
    (for example a single unmerged head from another peer) forced every later
    import to retreat to a critical version and replay the whole branch, and the
    map diff scanned every key of every touched map. Per-import cost grew with
    both the branch length and the map size: 400 small imports on a 2000-note doc
    with one stale head took ~2.4s natively; they now take ~70ms, flat per import
    (a linear import of the same chain takes ~50ms).

    The oplog now proves, per container, whether the concurrent old history
    touches anything that needs positional context. When it only touches registers
    the import replays from the current version; the affected maps are still
    resolved from history so persisted state that drops tombstones (deleted roots,
    dead containers) cannot influence the result. Map diffs in the conservative
    path are also restricted to the keys the update touched.

  • d9ddfba: Fix the richtext diff calculator's style table growing a duplicate entry for
    every re-replayed style op (e.g. checkout walks after a retreat).

loro-crdt-map@1.16.1

Patch Changes

  • 80a0e88: Make imports that are concurrent with the current version only on map/counter
    containers as fast as ordinary linear imports.

    Previously any concurrency between the new ops and the current version
    (for example a single unmerged head from another peer) forced every later
    import to retreat to a critical version and replay the whole branch, and the
    map diff scanned every key of every touched map. Per-import cost grew with
    both the branch length and the map size: 400 small imports on a 2000-note doc
    with one stale head took ~2.4s natively; they now take ~70ms, flat per import
    (a linear import of the same chain takes ~50ms).

    The oplog now proves, per container, whether the concurrent old history
    touches anything that needs positional context. When it only touches registers
    the import replays from the current version; the affected maps are still
    resolved from history so persisted state that drops tombstones (deleted roots,
    dead containers) cannot influence the result. Map diffs in the conservative
    path are also restricted to the keys the update touched.

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 20f9509 to c6947a6 Compare September 9, 2026 13:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants