Skip to content

fix(deps): update tiptap to ^3.3.0 (main) - #2025

Merged
enjeck merged 1 commit into
mainfrom
renovate/main-tiptap
Sep 1, 2025
Merged

fix(deps): update tiptap to ^3.3.0 (main)#2025
enjeck merged 1 commit into
mainfrom
renovate/main-tiptap

Conversation

@renovate

@renovate renovate Bot commented Aug 23, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@tiptap/extension-character-count (source) ^3.2.0 -> ^3.3.0 age confidence
@tiptap/extension-task-item (source) ^3.2.0 -> ^3.3.0 age confidence
@tiptap/extension-task-list (source) ^3.2.0 -> ^3.3.0 age confidence
@tiptap/starter-kit (source) ^3.2.0 -> ^3.3.0 age confidence
@tiptap/vue-2 (source) ^3.2.0 -> ^3.3.0 age confidence

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

ueberdosis/tiptap (@​tiptap/extension-character-count)

v3.3.0

Compare Source

Patch Changes

v3.2.2

Compare Source

Patch Changes

v3.2.1

Patch Changes
ueberdosis/tiptap (@​tiptap/extension-task-item)

v3.3.0

Compare Source

Releases
@​tiptap/core@​3.3.0
Minor Changes
  • 5423726: Make input rules and paste rules respect extension priority by registering
    them per-extension instead of aggregating them into a single global plugin.
Why
Previously all `addInputRules()` and `addPasteRules()` were gathered into one
global plugin which ran before the other plugins. That caused conflicts where
some extensions (for example mention/suggestion with `#`) could not preempt the
built-in heading input rule.
What changed
-   Input and paste rules are now created and registered at the position of the
    owning extension. This makes their execution order follow the extension
    sorting/`priority` mechanism.
-   Behavior is more predictable: extensions with higher `priority` can now take
    precedence over lower priority extensions' input/paste rules.
Migration & compatibility
-   This is a behavioral change. If you relied on the old global ordering (input
    rules always running before other plugins), you may observe different
    outcomes. In most cases this is desirable and fixes conflicts (like the
    `#` mention vs. heading shortcut), but be aware of the change.
-   If you need to force the previous behavior for a specific rule, you can:
    -   Register the rule as a ProseMirror plugin via `addProseMirrorPlugins()` on
        the extension and place it where you want it to run.
    -   Adjust the extension `priority` value so the extension sits earlier or
        later in the ordering.

If you have any questions or see regressions after upgrading, please open an
issue with a small repro and we'll help triage.
Patch Changes

  • 5423726: Fix paste rule handling for node views and defensively guard empty ranges.

    This patch ensures paste rules can correctly inspect node content when
    node-specific size metadata (nodeSize) is present, falling back to
    node.content.size when needed. It also skips empty or invalid node ranges
    before calling textBetween, preventing runtime errors originating from
    internal Fragment/Node traversals (for example: "Cannot read properties of
    undefined (reading 'nodeSize')").

@​tiptap/extension-unique-id@​3.3.0
Patch Changes

  • 5423726: Change the generateID option to accept a context object: { node, pos }.

    This lets ID generators access both the ProseMirror node and its pos within the document when creating IDs, enabling logic that depends on node content, type, or position.

    The change is backwards-compatible: existing generateID functions that ignore the new context will continue to work. Example usage:

    editor.use(UniqueID, {
  generateID: ({ node, pos }) => `${node.type.name}-${pos}-${uuidv4()}`,
})
@​tiptap/react@​3.3.0
Patch Changes

  • 5423726: Ensure ReactRenderer.destroy() removes the renderer DOM element when present.

    • When consumers append a ReactRenderer's .element to the DOM (for example many demos append it to document.body), previously calling destroy() removed the portal renderer but left the DOM node in place which could lead to accumulating .react-renderer elements.
    • destroy() now also removes the element from its parent node if present, preventing leaked DOM nodes / React roots.
@​tiptap/suggestion@​3.3.0
Patch Changes

  • 5423726: Add a safe API to exit suggestions and remove decorations.

    • Dispatching a metadata-only transaction with { exit: true } will now reliably deactivate the suggestion plugin and remove inline decorations.
    • Pressing Escape now triggers renderer.onExit and dispatches the exit meta, so suggestions close immediately without needing document edits.
    • Clicking outside the editor will also close active suggestions.
    • Exported exitSuggestion(view, pluginKey?) helper to programmatically close suggestions safely.

v3.2.2

Compare Source

Releases
@​tiptap/extension-unique-id@​3.2.2
Patch Changes

  • 1cab7ff: Change the generateID option to accept a context object: { node, pos }.

    This lets ID generators access both the ProseMirror node and its pos within the document when creating IDs, enabling logic that depends on node content, type, or position.

v3.2.1

Releases
@​tiptap/core@​3.2.1
Patch Changes
  • 6a2873f: Ensure drag previews for node views work correctly in Safari by attaching
    an offscreen clone of the node to the DOM while calling
    setDragImage, and by preserving the original element's pixel
    width/height so the preview matches the original. This prevents
    Safari from immediately cancelling the drag when a detached element is
    used as the drag image.
ueberdosis/tiptap (@​tiptap/starter-kit)

v3.3.0

Compare Source

Patch Changes

v3.2.2

Compare Source

Patch Changes

v3.2.1

Patch Changes

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Europe/Berlin, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added 3. to review Waiting for reviews dependencies Pull requests that update a dependency file labels Aug 23, 2025
@renovate
renovate Bot requested review from blizzz and enjeck as code owners August 23, 2025 00:29
@renovate renovate Bot added dependencies Pull requests that update a dependency file 3. to review Waiting for reviews labels Aug 23, 2025
@github-actions
github-actions Bot enabled auto-merge August 23, 2025 00:30
@renovate
renovate Bot force-pushed the renovate/main-tiptap branch from 783dded to 7a76cc1 Compare August 23, 2025 16:26
@renovate renovate Bot changed the title fix(deps): update tiptap to ^3.2.2 (main) fix(deps): update tiptap to ^3.3.0 (main) Aug 23, 2025
@renovate
renovate Bot force-pushed the renovate/main-tiptap branch 3 times, most recently from 3fe2066 to 16144dc Compare September 1, 2025 04:14
@renovate @enjeck
fix(deps): update tiptap to ^3.3.0
c0a5910 
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@enjeck
enjeck force-pushed the renovate/main-tiptap branch from 16144dc to c0a5910 Compare September 1, 2025 04:15
@enjeck
enjeck disabled auto-merge September 1, 2025 04:40
@enjeck
enjeck merged commit c67f272 into main Sep 1, 2025
50 of 52 checks passed
@enjeck
enjeck deleted the renovate/main-tiptap branch September 1, 2025 04:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@enjeck enjeck enjeck approved these changes
@github-actions github-actions[bot] github-actions[bot] approved these changes
@blizzz blizzz Awaiting requested review from blizzz blizzz is a code owner

Assignees

No one assigned

Labels

3. to review Waiting for reviews dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@enjeck