ui: bump the tiptap group in /ui with 6 updates

[dependabot]

Bumps the tiptap group in /ui with 6 updates:

Package	From	To
@tiptap/extension-image	3.29.2	3.30.1
@tiptap/extension-link	3.29.2	3.30.1
@tiptap/markdown	3.29.2	3.30.1
@tiptap/pm	3.29.2	3.30.1
@tiptap/react	3.29.2	3.30.1
@tiptap/starter-kit	3.29.2	3.30.1

Updates @tiptap/extension-image from 3.29.2 to 3.30.1

Release notes

Sourced from @​tiptap/extension-image's releases.

v3.30.1

@​tiptap/extension-table

Patch Changes

• Fixed table markdown pipe escaping so the extension loads on older Safari and iOS versions (WebKit before Safari 16.4).

@​tiptap/core

Patch Changes

• Added new ProseMirror helpers that check whether a value is a specific ProseMirror type.

v3.30.0

@​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.

... (truncated)

Changelog

Sourced from @​tiptap/extension-image's changelog.

3.30.1

Patch Changes

• Updated dependencies [abc8828]
  • @​tiptap/core@​3.30.1

3.30.0

Patch Changes

• Updated dependencies [0247d39]
• Updated dependencies [51909d3]
• Updated dependencies [3099eef]
  • @​tiptap/core@​3.30.0

Commits

• 4c4933d chore(release): release new stable release (#8181)
• 7901bc2 chore(release): release new stable release (#8142)
• See full diff in compare view

Updates @tiptap/extension-link from 3.29.2 to 3.30.1

Release notes

Sourced from @​tiptap/extension-link's releases.

v3.30.1

@​tiptap/extension-table

Patch Changes

• Fixed table markdown pipe escaping so the extension loads on older Safari and iOS versions (WebKit before Safari 16.4).

@​tiptap/core

Patch Changes

• Added new ProseMirror helpers that check whether a value is a specific ProseMirror type.

v3.30.0

@​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.

... (truncated)

Changelog

Sourced from @​tiptap/extension-link's changelog.

3.30.1

Patch Changes

• Updated dependencies [abc8828]
  • @​tiptap/core@​3.30.1
  • @​tiptap/pm@​3.30.1

3.30.0

Patch Changes

• Updated dependencies [0247d39]
• Updated dependencies [58a8953]
• Updated dependencies [51909d3]
• Updated dependencies [3099eef]
  • @​tiptap/core@​3.30.0
  • @​tiptap/pm@​3.30.0

Commits

• 4c4933d chore(release): release new stable release (#8181)
• 7901bc2 chore(release): release new stable release (#8142)
• 2036090 test(extension-link): guard non-link click selection with enableClickSelectio...
• See full diff in compare view

Updates @tiptap/markdown from 3.29.2 to 3.30.1

Release notes

Sourced from @​tiptap/markdown's releases.

v3.30.1

@​tiptap/extension-table

Patch Changes

• Fixed table markdown pipe escaping so the extension loads on older Safari and iOS versions (WebKit before Safari 16.4).

@​tiptap/core

Patch Changes

• Added new ProseMirror helpers that check whether a value is a specific ProseMirror type.

v3.30.0

@​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.

... (truncated)

Changelog

Sourced from @​tiptap/markdown's changelog.

3.30.1

Patch Changes

• Updated dependencies [abc8828]
  • @​tiptap/core@​3.30.1
  • @​tiptap/pm@​3.30.1

3.30.0

Patch Changes

• 03ba40e: Markdown with inline HTML such as an unclosed <b> tag no longer parses into an invalid document. The tag is dropped and its text is kept.
• Updated dependencies [0247d39]
• Updated dependencies [58a8953]
• Updated dependencies [51909d3]
• Updated dependencies [3099eef]
  • @​tiptap/core@​3.30.0
  • @​tiptap/pm@​3.30.0

Commits

• 4c4933d chore(release): release new stable release (#8181)
• 7901bc2 chore(release): release new stable release (#8142)
• c296281 fix(extension-list): let block math interrupt an ordered list item (#8167)
• 03ba40e fix(markdown): keep only inline content when parsing inline HTML (#8169)
• See full diff in compare view

Updates @tiptap/pm from 3.29.2 to 3.30.1

Release notes

Sourced from @​tiptap/pm's releases.

v3.30.1

@​tiptap/extension-table

Patch Changes

• Fixed table markdown pipe escaping so the extension loads on older Safari and iOS versions (WebKit before Safari 16.4).

@​tiptap/core

Patch Changes

• Added new ProseMirror helpers that check whether a value is a specific ProseMirror type.

v3.30.0

@​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.

... (truncated)

Changelog

Sourced from @​tiptap/pm's changelog.

3.30.1

3.30.0

Patch Changes

• 58a8953: Fix the ./schema-list export map pointing types at dist/schema/, which is not emitted. Tools that read the types condition directly could not resolve @tiptap/pm/schema-list.

Commits

• 4c4933d chore(release): release new stable release (#8181)
• 7901bc2 chore(release): release new stable release (#8142)
• 58a8953 fix(pm): point schema-list types at the emitted declaration files (#8157)
• See full diff in compare view

Updates @tiptap/react from 3.29.2 to 3.30.1

Release notes

Sourced from @​tiptap/react's releases.

v3.30.1

@​tiptap/extension-table

Patch Changes

• Fixed table markdown pipe escaping so the extension loads on older Safari and iOS versions (WebKit before Safari 16.4).

@​tiptap/core

Patch Changes

• Added new ProseMirror helpers that check whether a value is a specific ProseMirror type.

v3.30.0

@​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.

... (truncated)

Changelog

Sourced from @​tiptap/react's changelog.

3.30.1

Patch Changes

• Updated dependencies [abc8828]
  • @​tiptap/core@​3.30.1
  • @​tiptap/pm@​3.30.1

3.30.0

Minor Changes

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

... (truncated)

Commits

• 4c4933d chore(release): release new stable release (#8181)
• 7901bc2 chore(release): release new stable release (#8142)
• 3099eef feat(core): add Decorations API with framework widget renderers (#7902)
• 31e176c fix(react): avoid stale position when syncing node view selection (#8165)
• See full diff in compare view

Updates @tiptap/starter-kit from 3.29.2 to 3.30.1

Release notes

Sourced from @​tiptap/starter-kit's releases.

v3.30.1

@​tiptap/extension-table

Patch Changes

• Fixed table markdown pipe escaping so the extension loads on older Safari and iOS versions (WebKit before Safari 16.4).

@​tiptap/core

Patch Changes

• Added new ProseMirror helpers that check whether a value is a specific ProseMirror type.

v3.30.0

@​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.

... (truncated)

Changelog

Sourced from @​tiptap/starter-kit's changelog.

3.30.1

Patch Changes

• Updated dependencies [abc8828]
  • @​tiptap/core@​3.30.1
  • @​tiptap/extension-blockquote@​3.30.1
  • @​tiptap/extension-bold@​3.30.1
  • @​tiptap/extension-code@​3.30.1
  • @​tiptap/extension-code-block@​3.30.1
  • @​tiptap/extension-document@​3.30.1
  • @​tiptap/extension-hard-break@​3.30.1
  • @​tiptap/extension-heading@​3.30.1
  • @​tiptap/extension-horizontal-rule@​3.30.1
  • @​tiptap/extension-italic@​3.30.1
  • @​tiptap/extension-link@​3.30.1
  • @​tiptap/extension-list@​3.30.1
  • @​tiptap/extension-paragraph@​3.30.1
  • @​tiptap/extension-strike@​3.30.1
  • @​tiptap/extension-text@​3.30.1
  • @​tiptap/extension-underline@​3.30.1
  • @​tiptap/extensions@​3.30.1
  • @​tiptap/extension-list-item@​3.30.1
  • @​tiptap/extension-list-keymap@​3.30.1
  • @​tiptap/extension-bullet-list@​3.30.1
  • @​tiptap/extension-ordered-list@​3.30.1
  • @​tiptap/extension-dropcursor@​3.30.1
  • @​tiptap/extension-gapcursor@​3.30.1
  • @​tiptap/pm@​3.30.1

3.30.0

Patch Changes

• d18533a: 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 [0247d39]
• Updated dependencies [c296281]
• Updated dependencies [ceb0dac]
• Updated dependencies [58a8953]
• Updated dependencies [4ec64c7]
• Updated dependencies [51909d3]
• Updated dependencies [3099eef]
  • @​tiptap/extension-list@​3.30.0
  • @​tiptap/core@​3.30.0
  • @​tiptap/pm@​3.30.0
  • @​tiptap/extension-blockquote@​3.30.0
  • @​tiptap/extension-list-item@​3.30.0
  • @​tiptap/extension-list-keymap@​3.30.0
  • @​tiptap/extension-bullet-list@​3.30.0
  • @​tiptap/extension-ordered-list@​3.30.0

... (truncated)

Commits

• 4c4933d chore(release): release new stable release (#8181)
• 7901bc2 chore(release): release new stable release (#8142)
• d18533a fix(starter-kit): pin bundled @tiptap/* deps with workspace:* (#8160)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions