chore(deps): update tiptap to v3.33.0 #186
No reviewers
Labels
No labels
bug
duplicate
enhancement
future
help wanted
invalid
question
security
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/TeaLeaves!186
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/tiptap"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
3.32.2→3.33.03.32.2→3.33.03.32.2→3.33.03.32.2→3.33.0Release Notes
ueberdosis/tiptap (@tiptap/extension-link)
v3.33.0Compare Source
@tiptap/extension-collaboration
Minor Changes
With
enableContentCheck: true, shared content that does not fit the editor schema now emitscontentErrorinstead of being deleted. The editor pauses editing and sends no changes until compatible content arrives, so read-only users no longer send repairs that the server rejects.If you use
enableContentCheckwith collaboration and want the editor to keep repairing invalid content, turn the content check off.@tiptap/y-tiptap
Minor Changes
onInvalidContentsync option. When it is set, shared content that does not fit the editor schema stays in the shared document instead of being deleted. The editor shows what it can, pauses editing and sends no changes until compatible content arrives.v3.32.3@tiptap/core
Patch Changes
clearNodes()works in a chain with other node commands.@tiptap/extension-bubble-menu
Patch Changes
@tiptap/extension-code-block-lowlight
Patch Changes
@tiptap/extension-floating-menu
Patch Changes
@tiptap/extension-link
Patch Changes
defaultProtocoloption instead of always falling back tohttp.@tiptap/extensions
Patch Changes
includeChildrenis enabled.@tiptap/react
Patch Changes
setContentcreates React node views from inside an effect.@tiptap/vue-2
Patch Changes
@tiptap/vue-3
Patch Changes
@tiptap/y-tiptap
Minor Changes
Remove persistent position migrations to stop structural edits and undo or redo from adding migration history to collaborative documents. Saved relative positions no longer follow content that structural edits replace or move.
Existing migration entries are deleted when an editor opens and when later Yjs updates arrive. Yjs can reclaim their stored data when garbage collection is enabled. Document content and other shared data are unchanged. Upgrade all collaborating clients to stop older clients from writing new entries.
Documents that the server refuses to load need cleanup on the server before a client can repair them. With Yjs garbage collection disabled, deleting entries does not reclaim their stored data.
Configuration
📅 Schedule: (in timezone America/Chicago)
* 0-3 * * 1)🚦 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 these updates again.
This PR has been generated by Mend Renovate.