Repository navigation
chore: version packages - #1181
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 9, 2026 07:14
3862ccf to
46b7e75
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 9, 2026 14:45
46b7e75 to
67fc57a
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.17.0
Minor Changes
4f60d92: Return decode errors when fallible history operations first read an unreadable change block, preserving document state instead of panicking during lazy DAG loading.
Keep attached imports atomic even after all DAG headers have been loaded: unparsed change-block bodies still require rollback protection. Share the existing version snapshot between rollback journals to avoid two extra copies of the version vector. Legacy infallible range readers continue skipping only the damaged block while recording the failure.
state_vv/version, JSON update export, cursor lookup,apply_diffrollback, shallow imports, andfork_atreturnDecodeErrorinstead of panicking or wrapping the failure asUnknown.state_vvandexport_json_updatesnow returnLoroResult.try_state_vv,try_export_json_updates, andtry_get_cursor_posreport the same failure.CannotFindRelativePositionis#[non_exhaustive]and gainsHistoryUnreadable.LoroEncodeErrorgainsDecodeError.Rust compatibility:
ChangeTravelErrorgainsHistoryUnreadable(LoroError)and is now#[non_exhaustive]; downstream exhaustive matches must add a wildcard arm.FrontiersNotIncludedchanges from a unit struct to a struct with a private field plus a same-named constant. Construction via that constant still compiles, but an exhaustivematchofErr(FrontiersNotIncluded)does not (E0004): thehistory_error: Some(_)pattern cannot be written from another crate (E0451) because the field is private. Downstream must useErr(_). An unreadable-history error is not equal to theFrontiersNotIncludedconstant.Patch Changes
a02843a: Fix quadratic local tree moves when interleaved with queries or failed edits on deleted containers by releasing the revivable deletion cache's table on invalidation.
a02843a: Preserve the full text style configuration, including the default for previously unused style keys, when calling
fork()orforkAt().ca372b4: Reduce known-history comparison costs for snapshot-loaded documents while preserving peer-id reuse detection. Snapshot updates allocate only new history in the document arena and avoid cloning discarded changes.
Avoid unnecessary rollback scopes for detached Text imports while retaining validation of pending movable-list operations.
Keep import rollback decisions consistent across concurrent attach/detach, and fall back to ordinary history parsing when a cold-block comparison is ineligible.
loro-crdt-map@1.17.0
Minor Changes
4f60d92: Return decode errors when fallible history operations first read an unreadable change block, preserving document state instead of panicking during lazy DAG loading.
Keep attached imports atomic even after all DAG headers have been loaded: unparsed change-block bodies still require rollback protection. Share the existing version snapshot between rollback journals to avoid two extra copies of the version vector. Legacy infallible range readers continue skipping only the damaged block while recording the failure.
state_vv/version, JSON update export, cursor lookup,apply_diffrollback, shallow imports, andfork_atreturnDecodeErrorinstead of panicking or wrapping the failure asUnknown.state_vvandexport_json_updatesnow returnLoroResult.try_state_vv,try_export_json_updates, andtry_get_cursor_posreport the same failure.CannotFindRelativePositionis#[non_exhaustive]and gainsHistoryUnreadable.LoroEncodeErrorgainsDecodeError.Rust compatibility:
ChangeTravelErrorgainsHistoryUnreadable(LoroError)and is now#[non_exhaustive]; downstream exhaustive matches must add a wildcard arm.FrontiersNotIncludedchanges from a unit struct to a struct with a private field plus a same-named constant. Construction via that constant still compiles, but an exhaustivematchofErr(FrontiersNotIncluded)does not (E0004): thehistory_error: Some(_)pattern cannot be written from another crate (E0451) because the field is private. Downstream must useErr(_). An unreadable-history error is not equal to theFrontiersNotIncludedconstant.Patch Changes
a02843a: Fix quadratic local tree moves when interleaved with queries or failed edits on deleted containers by releasing the revivable deletion cache's table on invalidation.
a02843a: Preserve the full text style configuration, including the default for previously unused style keys, when calling
fork()orforkAt().ca372b4: Reduce known-history comparison costs for snapshot-loaded documents while preserving peer-id reuse detection. Snapshot updates allocate only new history in the document arena and avoid cloning discarded changes.
Avoid unnecessary rollback scopes for detached Text imports while retaining validation of pending movable-list operations.
Keep import rollback decisions consistent across concurrent attach/detach, and fall back to ordinary history parsing when a cold-block comparison is ineligible.