Skip to content

chore(deps): update tiptap monorepo to v3.30.0 - #434

Open
renovate[bot] wants to merge 1 commit into
chore/all-my-stuffsfrom
renovate/tiptap-monorepo
Open

chore(deps): update tiptap monorepo to v3.30.0#434
renovate[bot] wants to merge 1 commit into
chore/all-my-stuffsfrom
renovate/tiptap-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jul 10, 2026 •
edited
Loading

Copy link
Copy Markdown

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@tiptap/core (source) 3.27.1 → 3.30.0 age confidence
@tiptap/extension-color (source) 3.27.1 → 3.30.0 age confidence
@tiptap/extension-gapcursor (source) 3.27.1 → 3.30.0 age confidence
@tiptap/extension-highlight (source) 3.27.1 → 3.30.0 age confidence
@tiptap/extension-table (source) 3.27.1 → 3.30.0 age confidence
@tiptap/extension-text-align (source) 3.27.1 → 3.30.0 age confidence
@tiptap/extension-text-style (source) 3.27.1 → 3.30.0 age confidence
@tiptap/extensions (source) 3.27.1 → 3.30.0 age confidence
@tiptap/pm (source) 3.27.1 → 3.30.0 age confidence
@tiptap/starter-kit (source) 3.27.1 → 3.30.0 age confidence
@tiptap/vue-3 (source) 3.27.1 → 3.30.0 age confidence

Release Notes

ueberdosis/tiptap (@​tiptap/core)

v3.30.0

Compare Source

Minor Changes

  • 0247d39: ListKeymap now registers a Tab shortcut that sinks a top-level textblock into the previous list's last item. Pressing Tab at the start of a paragraph right after a bullet/ordered/task list moves the paragraph inside the last list item. The handler does nothing when the cursor is already inside a list item (sinkListItem keeps working), when there is no list before the paragraph, when the caret is mid-textblock, or when the selection is not a text selection (for example a gap cursor).

    @tiptap/core also exposes a new getPreviousBlockSibling($pos) helper that returns the block-level sibling before the cursor's textblock, or null at the first child of the block parent.

  • 3099eef: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

Patch Changes
  • 51909d3: Fixed insertContent, insertContentAt and setContent failing when prosemirror-model is loaded more than once.
  • Updated dependencies [58a8953]

v3.29.2

Compare Source

Patch Changes

v3.29.1

Compare Source

Patch Changes

v3.29.0

Compare Source

Patch Changes
  • d26840f: Fix a TypeScript build error in isAndroid() where comparing navigator.platform against the literal 'Android' with === could fail to compile under some lib.dom.d.ts typings ("types have no overlap"). Switched to the same .includes() pattern already used by isiOS(), which is not affected by this TypeScript narrowing issue. No runtime behavior change.
  • 935e63f: Fixed a bug where deleting an AllSelection (for example right after Ctrl/Cmd+A) left a lingering "phantom" selection highlight over the emptied document instead of a text cursor. deleteSelection now collapses the selection to a cursor.
  • b4c5a2d: Fix input rules crashing when the matched text spans an inline atom node like a mention.
  • a963d48: Node view getPos() now returns undefined instead of throwing when the position cannot be resolved yet, for example when React 19 renders a node view component while the editor view is still updating.
  • 51f45b6: Fixed onContentError throwing when calling editor.commands from inside the handler on initial load with invalid content. The editor now has a usable state (seeded from the stripped fallback document) before onContentError fires.
  • 0f63969: Fix editor.$pos() returning the wrong node inside container nodes, for example the list item instead of the list.
  • 9acaa65: Add insertDefaultBlock to insert the default textblock allowed at a position. It accepts an optional position, attributes, content, and selection-update option.
  • Updated dependencies [e150ee0]

v3.28.0

Compare Source

Patch Changes

v3.27.4

Compare Source

Patch Changes

v3.27.3

Compare Source

Patch Changes
  • 023f98c: Fix deleteSelection to delete content across all selection ranges instead of only the first range. This restores multi-cell table selections and other custom selections with multiple ranges.

v3.27.2

Compare Source

Patch Changes
ueberdosis/tiptap (@​tiptap/extension-color)

v3.30.0

Compare Source

Patch Changes

v3.29.2

Compare Source

Patch Changes

v3.29.1

Compare Source

Patch Changes

v3.29.0

Compare Source

Patch Changes

v3.28.0

Compare Source

Patch Changes

v3.27.4

Compare Source

Patch Changes

v3.27.3

Compare Source

Patch Changes

v3.27.2

Compare Source

Patch Changes
ueberdosis/tiptap (@​tiptap/extension-gapcursor)

v3.30.0

Compare Source

Patch Changes

v3.29.2

Compare Source

Patch Changes

v3.29.1

Compare Source

Patch Changes

v3.29.0

Compare Source

Patch Changes

v3.28.0

Compare Source

Patch Changes

v3.27.4

Compare Source

Patch Changes

v3.27.3

Compare Source

Patch Changes

v3.27.2

Compare Source

Patch Changes
ueberdosis/tiptap (@​tiptap/extension-highlight)

v3.30.0

Compare Source

Patch Changes

v3.29.2

Compare Source

Patch Changes

v3.29.1

Compare Source

Patch Changes

v3.29.0

Compare Source

Patch Changes

v3.28.0

Compare Source

Patch Changes

v3.27.4

Compare Source

@​tiptap/extensions
Patch Changes
  • 0fde1e8: Fixed the Selection extension leaving the native browser selection visible on blur, where it overlapped the selection decoration. The native selection is now cleared on blur and restored on focus.
  • @​tiptap/core@​3.27.4
@​tiptap/extension-blockquote
Patch Changes
  • 0fde1e8: Fix a crash when pressing backspace at the very start of the document with a leading image. The blockquote backspace handler dereferenced an undefined parent at the top (doc) level, throwing TypeError: Cannot read properties of undefined (reading 'type'). It now bails out so backspace is a no-op at the document start.
  • 0fde1e8: Add @tiptap/pm as a peer dependency so bundlers resolve ProseMirror packages from the app instead of duplicating prosemirror-model inside @tiptap/extension-blockquote.
  • @​tiptap/core@​3.27.4
@​tiptap/extension-table
Patch Changes
  • 0fde1e8: Fix <col width> in a table's <colgroup> being ignored when parsing HTML. The width of the first column was always dropped because the cell index 0 failed a truthiness check, and header cells (<th>) never read the colgroup at all. Both table cells and table headers now fall back to the matching <col> element's width attribute when they have no colwidth attribute of their own.
  • 0fde1e8: Fix pipe characters inside backtick inline code spans being incorrectly treated as table column delimiters in both leading-pipe and pipeless (no leading |) GFM tables. Cells containing expressions like `||` or `a || b` now parse correctly instead of splitting into extra columns and losing their code formatting.
  • @​tiptap/core@​3.27.4
@​tiptap/extension-list
Patch Changes
  • 0fde1e8: Fix a markdown parsing bug where a plain bullet (- item) nested under a task-list parent (- [ ]) was silently dropped from the parsed document. The task-list tokenizer's nested parser stopped at the first non-checkbox line and discarded everything after it; that remainder is now lexed and kept as sibling blocks (a bullet list or paragraph inside the parent task item), matching how mixed lists already behave at the top level.
  • @​tiptap/core@​3.27.4
@​tiptap/react
Patch Changes
  • 0fde1e8: Add a use client directive so @tiptap/react can be imported from React Server Components without crashing. Core symbols re-exported through @tiptap/react now cross the client boundary too, so import them from @tiptap/core directly in server code.

v3.27.3

Compare Source

Patch Changes

v3.27.2

Compare Source

Patch Changes
ueberdosis/tiptap (@​tiptap/extension-table)

v3.30.0

Compare Source

Patch Changes

v3.29.2

Compare Source

Patch Changes

v3.29.1

Compare Source

Patch Changes

v3.29.0

Compare Source

Patch Changes
  • 093573a: Fix inserting a table with an empty cell or header (e.g. via insertContent/insertContentAt) throwing RangeError: Invalid content for node tableCell/tableHeader: <>. Empty <td>/<th> elements are now backfilled with the cell's default block content, matching the behavior you already get from setContent.
  • 8649f2f: Keep line breaks inside table cells when serializing to markdown. Hard breaks and paragraph breaks in a cell are now written as <br> instead of being collapsed into a space, so they survive a parse/serialize round trip.
  • Updated dependencies [d26840f]
  • Updated dependencies [e150ee0]
  • Updated dependencies [935e63f]
  • Updated dependencies [b4c5a2d]
  • Updated dependencies [a963d48]
  • Updated dependencies [51f45b6]
  • Updated dependencies [0f63969]
  • Updated dependencies [9acaa65]

v3.28.0

Compare Source

Patch Changes

v3.27.4

Compare Source

Patch Changes
  • 246e1e8: Fix <col width> in a table's <colgroup> being ignored when parsing HTML. The width of the first column was always dropped because the cell index 0 failed a truthiness check, and header cells (<th>) never read the colgroup at all. Both table cells and table headers now fall back to the matching <col> element's width attribute when they have no colwidth attribute of their own.
  • edaac47: Fix pipe characters inside backtick inline code spans being incorrectly treated as table column delimiters in both leading-pipe and pipeless (no leading |) GFM tables. Cells containing expressions like `||` or `a || b` now parse correctly instead of splitting into extra columns and losing their code formatting.

v3.27.3

Compare Source

Patch Changes

v3.27.2

Compare Source

Patch Changes
ueberdosis/tiptap (@​tiptap/extension-text-align)

v3.30.0

Compare Source

Patch Changes

v3.29.2

Compare Source

Patch Changes

v3.29.1

Compare Source

Patch Changes

v3.29.0

Compare Source

Patch Changes

v3.28.0

Compare Source

Patch Changes

v3.27.4

Compare Source

@​tiptap/extensions
Patch Changes
  • 0fde1e8: Fixed the Selection extension leaving the native browser selection visible on blur, where it overlapped the selection decoration. The native selection is now cleared on blur and restored on focus.
  • @​tiptap/core@​3.27.4
@​tiptap/extension-blockquote
Patch Changes
  • 0fde1e8: Fix a crash when pressing backspace at the very start of the document with a leading image. The blockquote backspace handler dereferenced an undefined parent at the top (doc) level, throwing TypeError: Cannot read properties of undefined (reading 'type'). It now bails out so backspace is a no-op at the document start.
  • 0fde1e8: Add @tiptap/pm as a peer dependency so bundlers resolve ProseMirror packages from the app instead of duplicating prosemirror-model inside @tiptap/extension-blockquote.
  • @​tiptap/core@​3.27.4
@​tiptap/extension-table
Patch Changes
  • 0fde1e8: Fix <col width> in a table's <colgroup> being ignored when parsing HTML. The width of the first column was always dropped because the cell index 0 failed a truthiness check, and header cells (<th>) never read the colgroup at all. Both table cells and table headers now fall back to the matching <col> element's width attribute when they have no colwidth attribute of their own.
  • 0fde1e8: Fix pipe characters inside backtick inline code spans being incorrectly treated as table column delimiters in both leading-pipe and pipeless (no leading |) GFM tables. Cells containing expressions like `||` or `a || b` now parse correctly instead of splitting into extra columns and losing their code formatting.
  • @​tiptap/core@​3.27.4
@​tiptap/extension-list
Patch Changes
  • 0fde1e8: Fix a markdown parsing bug where a plain bullet (- item) nested under a task-list parent (- [ ]) was silently dropped from the parsed document. The task-list tokenizer's nested parser stopped at the first non-checkbox line and discarded everything after it; that remainder is now lexed and kept as sibling blocks (a bullet list or paragraph inside the parent task item), matching how mixed lists already behave at the top level.
  • @​tiptap/core@​3.27.4
@​tiptap/react
Patch Changes
  • 0fde1e8: Add a use client directive so @tiptap/react can be imported from React Server Components without crashing. Core symbols re-exported through @tiptap/react now cross the client boundary too, so import them from @tiptap/core directly in server code.

v3.27.3

Compare Source

Patch Changes

v3.27.2

Compare Source

Patch Changes
ueberdosis/tiptap (@​tiptap/extension-text-style)

v3.30.0

Compare Source

Patch Changes

v3.29.2

Compare Source

Patch Changes

v3.29.1

Compare Source

Patch Changes

v3.29.0

Compare Source

Patch Changes

v3.28.0

Compare Source

Patch Changes

v3.27.4

Compare Source

Patch Changes

v3.27.3

Compare Source

Patch Changes

v3.27.2

Compare Source

Patch Changes
ueberdosis/tiptap (@​tiptap/extensions)

v3.30.0

Compare Source

@​tiptap/vue-2
Minor Changes

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

Patch Changes
@​tiptap/extension-list
Minor Changes

  • ceb0dac: ListKeymap now registers a Tab shortcut that sinks a top-level textblock into the previous list's last item. Pressing Tab at the start of a paragraph right after a bullet/ordered/task list moves the paragraph inside the last list item. The handler does nothing when the cursor is already inside a list item (sinkListItem keeps working), when there is no list before the paragraph, when the caret is mid-textblock, or when the selection is not a text selection (for example a gap cursor).

    @tiptap/core also exposes a new getPreviousBlockSibling($pos) helper that returns the block-level sibling before the cursor's textblock, or null at the first child of the block parent.

Patch Changes
  • ceb0dac: Parse block math that follows an ordered list item without a blank line, both after the list and indented inside the item, instead of pulling it into the item's text.
  • ceb0dac: TaskItem: the checkbox label now also fills the wrapping label element, so accessibility audits no longer flag it as empty.
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]
@​tiptap/core
Minor Changes

  • ceb0dac: ListKeymap now registers a Tab shortcut that sinks a top-level textblock into the previous list's last item. Pressing Tab at the start of a paragraph right after a bullet/ordered/task list moves the paragraph inside the last list item. The handler does nothing when the cursor is already inside a list item (sinkListItem keeps working), when there is no list before the paragraph, when the caret is mid-textblock, or when the selection is not a text selection (for example a gap cursor).

    @tiptap/core also exposes a new getPreviousBlockSibling($pos) helper that returns the block-level sibling before the cursor's textblock, or null at the first child of the block parent.

  • ceb0dac: New Decorations API

    Finally the decorations API is here! Even though Decorations itself are nothing new in ProseMirror, the new API makes it much easier to use them in Tiptap without leaving your extensions.

    Decorations change how the document looks without changing the document itself. Highlighting search results, marking spelling mistakes, showing collaborator cursors, putting a drag handle next to every block.

    Until now you had to write a ProseMirror plugin by hand for this, keep the decoration set in plugin state, and map it forward on every transaction. Extensions can now declare decorations directly with a new addDecorations() hook.

    addDecorations() {
  return {
    create: ({ state }) =>
      // findMatches can be any function that returns an array of { from, to } ranges
      findMatches(state.doc).map(match =>
        Decoration.Inline(match.from, match.to, { class: 'highlight' }),
      ),
  }
}

    There are three kinds. Decoration.Inline() styles a range of text. Decoration.Node() puts attributes on a block's DOM element. Decoration.Widget() renders your own element at a single position.

    Every extension that declares decorations is collected into one plugin, so several extensions can decorate the same document without fighting over it.

    Doing less work on every keystroke

    By default decorations are rebuilt whenever the document changes. That is fine for small documents and wasteful for large ones, so there are two ways to narrow it down.

    shouldUpdate() skips transactions you do not care about. If your decorations only depend on headings, ignore everything else.

    update: 'changedRanges' together with createInRange() only rescans the blocks that actually changed. On a long document this is the difference between scanning the whole thing on every keystroke and scanning one paragraph.

    For decorations driven by data outside the editor, like comments loaded from a server, use update: 'manual' and refresh them yourself with editor.commands.updateDecorations().

    React and Vue components as widgets

    ReactWidgetRenderer and VueWidgetRenderer render a real component into a widget decoration, inside your existing app context. Providers, context and stores work as usual.

    Widgets take a key. Reuse the same key and the component instance stays mounted while the document changes around it, so local state such as an open menu, a counter or a half-typed input survives editing. Use a stable id from your own data, not a position or a list index, otherwise the component remounts and loses that state.

    Widgets also accept the ProseMirror options side, relaxedSide, stopEvent and ignoreSelection.

    Documentation

Patch Changes
  • ceb0dac: Fixed insertContent, insertContentAt and setContent failing when prosemirror-model is loaded more than once.
  • Updated dependencies [ceb0dac]
@​tiptap/starter-kit
Patch Changes
  • ceb0dac: StarterKit now pins its bundled @tiptap/* dependencies to the exact version it was released with, so installing a specific StarterKit version gives you that version's extension set instead of the newest one.
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]
  • Updated dependencies [ceb0dac]

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Paris)

  • Branch creation
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
  • Automerge
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)

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

@sharevb
sharevb force-pushed the chore/all-my-stuffs branch 3 times, most recently from 1cc77eb to 02df0f3 Compare July 11, 2026 15:17
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from e2db253 to d59b4eb Compare July 12, 2026 11:38
@sharevb
sharevb force-pushed the chore/all-my-stuffs branch 2 times, most recently from 41fa755 to 0620f57 Compare July 12, 2026 14:58
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from d59b4eb to 791a779 Compare July 12, 2026 16:18
@sharevb
sharevb force-pushed the chore/all-my-stuffs branch from e7d0ce8 to 41464cf Compare July 12, 2026 19:04
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from 791a779 to a57009c Compare July 12, 2026 19:08
@sharevb
sharevb force-pushed the chore/all-my-stuffs branch from 138e700 to c6447be Compare July 12, 2026 21:05
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from a57009c to 0bfa662 Compare July 12, 2026 21:07
@sharevb
sharevb force-pushed the chore/all-my-stuffs branch from c6447be to 23dc0d4 Compare July 12, 2026 21:11
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch 2 times, most recently from d2a26c6 to b95cdbe Compare July 13, 2026 20:43
@renovate renovate Bot changed the title chore(deps): update tiptap monorepo to v3.27.3 chore(deps): update tiptap monorepo to v3.27.4 Jul 13, 2026
@sharevb
sharevb force-pushed the chore/all-my-stuffs branch from 74a0eb2 to 96a2079 Compare July 13, 2026 21:16
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from b95cdbe to 41323a2 Compare July 16, 2026 01:01
@renovate renovate Bot changed the title chore(deps): update tiptap monorepo to v3.27.4 chore(deps): update tiptap monorepo to v3.28.0 Jul 16, 2026
@sharevb
sharevb force-pushed the chore/all-my-stuffs branch from 18f53d0 to 44f13a5 Compare July 16, 2026 06:49
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from 41323a2 to 1283440 Compare July 16, 2026 15:03
@sharevb
sharevb force-pushed the chore/all-my-stuffs branch 2 times, most recently from 6a1819c to 65955d9 Compare July 19, 2026 19:02
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch 3 times, most recently from 89ec136 to aeaee00 Compare July 24, 2026 15:04
@renovate renovate Bot changed the title chore(deps): update tiptap monorepo to v3.28.0 chore(deps): update tiptap monorepo to v3.29.0 Jul 24, 2026
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from aeaee00 to e3f2edb Compare July 27, 2026 14:30
@renovate renovate Bot changed the title chore(deps): update tiptap monorepo to v3.29.0 chore(deps): update tiptap monorepo to v3.29.1 Jul 27, 2026
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from e3f2edb to 178b660 Compare July 27, 2026 19:50
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from 178b660 to f40450c Compare August 8, 2026 19:09
@renovate renovate Bot changed the title chore(deps): update tiptap monorepo to v3.29.1 chore(deps): update tiptap monorepo to v3.29.2 Aug 8, 2026
@renovate
renovate Bot force-pushed the renovate/tiptap-monorepo branch from f40450c to 5d0f897 Compare August 11, 2026 11:07
@renovate renovate Bot changed the title chore(deps): update tiptap monorepo to v3.29.2 chore(deps): update tiptap monorepo to v3.30.0 Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants