chore(deps): update dependency loro-crdt to ^1.13.9 - #1841
Merged
Conversation
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 contains the following updates:
^1.13.8→^1.13.9Release Notes
loro-dev/loro (loro-crdt)
v1.13.9Compare Source
Patch Changes
ddc47ec: Retreat the conservative replay base to the latest single-head criticalversion 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 statecould 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 alreadycovers 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.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.