chore: version packages

[github-actions]

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.13.5

Patch Changes

• 1727258: Improve text insert and snapshot import performance by avoiding duplicate text boundary validation and skipping eager imported change block parsing.

• 52d8168: Recover two per-operation editing slowdowns regressed since 1.11.

  Both are constant-factor regressions on the per-op (auto-commit) editing path
  introduced by the lazy-snapshot work in perf: reduce snapshot read memory retention #985, measured against the 1.11.1
  release.

  1. Every MapHandler/ListHandler/MovableListHandler insert validated its
     value with ensure_no_regular_container_value, which heap-allocated a Vec
     on each call even for scalar values (the common case). A scalar fast-path now
     skips the allocation and traversal entirely. map create 10^4 key:
     ~19.4ms -> ~10.7ms.
  2. The per-op text bounds check (TextHandler::len/len_unicode/len_utf16)
     took two DocState locks — one to check whether the container state was
     decoded, then another to query the length. These are now consolidated into a
     single DocState::get_text_len that takes one lock and one container-store
     lookup. The lazy-snapshot memory behavior is preserved: a still-lazy
     container reads its cached length metadata without materializing the full
     richtext state. bench_text B4 apply (per-op text editing): ~389ms -> ~352ms.

loro-crdt-map@1.13.5

Patch Changes

• 1727258: Improve text insert and snapshot import performance by avoiding duplicate text boundary validation and skipping eager imported change block parsing.

• 52d8168: Recover two per-operation editing slowdowns regressed since 1.11.

  Both are constant-factor regressions on the per-op (auto-commit) editing path
  introduced by the lazy-snapshot work in perf: reduce snapshot read memory retention #985, measured against the 1.11.1
  release.

  1. Every MapHandler/ListHandler/MovableListHandler insert validated its
     value with ensure_no_regular_container_value, which heap-allocated a Vec
     on each call even for scalar values (the common case). A scalar fast-path now
     skips the allocation and traversal entirely. map create 10^4 key:
     ~19.4ms -> ~10.7ms.
  2. The per-op text bounds check (TextHandler::len/len_unicode/len_utf16)
     took two DocState locks — one to check whether the container state was
     decoded, then another to query the length. These are now consolidated into a
     single DocState::get_text_len that takes one lock and one container-store
     lookup. The lazy-snapshot memory behavior is preserved: a still-lazy
     container reads its cached length metadata without materializing the full
     richtext state. bench_text B4 apply (per-op text editing): ~389ms -> ~352ms.