github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-03-18 13:01:03 -05:00
Code Issues 308 Packages Projects Releases 100 Wiki Activity

[PR #17097] [MERGED] build(deps): bump @tiptap/extension-highlight from 3.0.7 to 3.3.0 #11120

New Issue
Closed
opened 2025-11-11 19:22:39 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-11 19:22:39 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/17097
Author: @dependabot[bot]
Created: 9/1/2025
Status: ✅ Merged
Merged: 9/1/2025
Merged by: @tjbck

Base: dev ← Head: dependabot/npm_and_yarn/dev/tiptap/extension-highlight-3.3.0

📝 Commits (1)

  • 201eaa9 build(deps): bump @tiptap/extension-highlight from 3.0.7 to 3.3.0

📊 Changes

2 files changed (+6 additions, -6 deletions)

View changed files

📝 package-lock.json (+5 -5)
📝 package.json (+1 -1)

📄 Description

Bumps @tiptap/extension-highlight from 3.0.7 to 3.3.0.

Release notes

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

v3.3.0

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')").

... (truncated)

Changelog

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

3.3.0

Patch Changes

  • Updated dependencies [5423726]
  • Updated dependencies [5423726]
    • @​tiptap/core@​3.3.0

3.2.2

Patch Changes

  • @​tiptap/core@​3.2.2

3.2.1

Patch Changes

  • Updated dependencies [6a2873f]
    • @​tiptap/core@​3.2.1

3.2.0

Patch Changes

  • Updated dependencies [5056e3e]
    • @​tiptap/core@​3.2.0

3.1.0

Patch Changes

  • @​tiptap/core@​3.1.0

3.0.9

Patch Changes

  • @​tiptap/core@​3.0.9

3.0.8

Patch Changes

  • @​tiptap/core@​3.0.8
Commits

Dependabot compatibility score

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 merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/17097 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 9/1/2025 **Status:** ✅ Merged **Merged:** 9/1/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `dependabot/npm_and_yarn/dev/tiptap/extension-highlight-3.3.0` --- ### 📝 Commits (1) - [`201eaa9`](https://github.com/open-webui/open-webui/commit/201eaa965567188ccfc55aede2df822f7d25380f) build(deps): bump @tiptap/extension-highlight from 3.0.7 to 3.3.0 ### 📊 Changes **2 files changed** (+6 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+5 -5) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [@tiptap/extension-highlight](https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight) from 3.0.7 to 3.3.0. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/ueberdosis/tiptap/releases"><code>@​tiptap/extension-highlight</code>'s releases</a>.</em></p> <blockquote> <h2>v3.3.0</h2> <h1>Releases</h1> <h2><code>@​tiptap/core</code><a href="https://github.com/3"><code>@​3</code></a>.3.0</h2> <h3>Minor Changes</h3> <ul> <li> <p>5423726: Make input rules and paste rules respect extension <code>priority</code> by registering them per-extension instead of aggregating them into a single global plugin.</p> <h2>Why</h2> <p>Previously all <code>addInputRules()</code> and <code>addPasteRules()</code> were gathered into one global plugin which ran before the other plugins. That caused conflicts where some extensions (for example mention/suggestion with <code>#</code>) could not preempt the built-in heading input rule.</p> <h2>What changed</h2> <ul> <li>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/<code>priority</code> mechanism.</li> <li>Behavior is more predictable: extensions with higher <code>priority</code> can now take precedence over lower priority extensions' input/paste rules.</li> </ul> <h2>Migration &amp; compatibility</h2> <ul> <li>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 <code>#</code> mention vs. heading shortcut), but be aware of the change.</li> <li>If you need to force the previous behavior for a specific rule, you can: <ul> <li>Register the rule as a ProseMirror plugin via <code>addProseMirrorPlugins()</code> on the extension and place it where you want it to run.</li> <li>Adjust the extension <code>priority</code> value so the extension sits earlier or later in the ordering.</li> </ul> </li> </ul> <p>If you have any questions or see regressions after upgrading, please open an issue with a small repro and we'll help triage.</p> </li> </ul> <h3>Patch Changes</h3> <ul> <li> <p>5423726: Fix paste rule handling for node views and defensively guard empty ranges.</p> <p>This patch ensures paste rules can correctly inspect node content when node-specific size metadata (<code>nodeSize</code>) is present, falling back to <code>node.content.size</code> when needed. It also skips empty or invalid node ranges before calling <code>textBetween</code>, preventing runtime errors originating from internal Fragment/Node traversals (for example: &quot;Cannot read properties of undefined (reading 'nodeSize')&quot;).</p> </li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ueberdosis/tiptap/blob/develop/packages/extension-highlight/CHANGELOG.md"><code>@​tiptap/extension-highlight</code>'s changelog</a>.</em></p> <blockquote> <h2>3.3.0</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies [5423726]</li> <li>Updated dependencies [5423726] <ul> <li><code>@​tiptap/core</code><a href="https://github.com/3"><code>@​3</code></a>.3.0</li> </ul> </li> </ul> <h2>3.2.2</h2> <h3>Patch Changes</h3> <ul> <li><code>@​tiptap/core</code><a href="https://github.com/3"><code>@​3</code></a>.2.2</li> </ul> <h2>3.2.1</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies [6a2873f] <ul> <li><code>@​tiptap/core</code><a href="https://github.com/3"><code>@​3</code></a>.2.1</li> </ul> </li> </ul> <h2>3.2.0</h2> <h3>Patch Changes</h3> <ul> <li>Updated dependencies [5056e3e] <ul> <li><code>@​tiptap/core</code><a href="https://github.com/3"><code>@​3</code></a>.2.0</li> </ul> </li> </ul> <h2>3.1.0</h2> <h3>Patch Changes</h3> <ul> <li><code>@​tiptap/core</code><a href="https://github.com/3"><code>@​3</code></a>.1.0</li> </ul> <h2>3.0.9</h2> <h3>Patch Changes</h3> <ul> <li><code>@​tiptap/core</code><a href="https://github.com/3"><code>@​3</code></a>.0.9</li> </ul> <h2>3.0.8</h2> <h3>Patch Changes</h3> <ul> <li><code>@​tiptap/core</code><a href="https://github.com/3"><code>@​3</code></a>.0.8</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ueberdosis/tiptap/commit/ba8d13fa83e17689b03a1fdee131fb870b0e4586"><code>ba8d13f</code></a> chore(release): publish a new release version (<a href="https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight/issues/6863">#6863</a>)</li> <li><a href="https://github.com/ueberdosis/tiptap/commit/1a232042ba67c77b4fc663f8383603e0cf4907e1"><code>1a23204</code></a> chore(release): publish a new release version (<a href="https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight/issues/6860">#6860</a>)</li> <li><a href="https://github.com/ueberdosis/tiptap/commit/11d430c9aed67575d852407a9a03fd1e7e783457"><code>11d430c</code></a> chore(release): publish a new release version (<a href="https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight/issues/6853">#6853</a>)</li> <li><a href="https://github.com/ueberdosis/tiptap/commit/71db1f26e8a998c1675f183d99eee4291f45e50f"><code>71db1f2</code></a> chore(release): publish a new release version (<a href="https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight/issues/6792">#6792</a>)</li> <li><a href="https://github.com/ueberdosis/tiptap/commit/03cfa845dd323e7342696dc959355f415a835187"><code>03cfa84</code></a> chore(release): publish a new release version (<a href="https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight/issues/6791">#6791</a>)</li> <li><a href="https://github.com/ueberdosis/tiptap/commit/224cb2c77a7921e62b18f4b510bb314b582926df"><code>224cb2c</code></a> chore(release): publish a new release version (<a href="https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight/issues/6753">#6753</a>)</li> <li><a href="https://github.com/ueberdosis/tiptap/commit/ed0dd524d21ef5eb82f4e6f8d85b902f3241925b"><code>ed0dd52</code></a> chore(release): publish a new release version (<a href="https://github.com/ueberdosis/tiptap/tree/HEAD/packages/extension-highlight/issues/6750">#6750</a>)</li> <li>See full diff in <a href="https://github.com/ueberdosis/tiptap/commits/v3.3.0/packages/extension-highlight">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=@tiptap/extension-highlight&package-manager=npm_and_yarn&previous-version=3.0.7&new-version=3.3.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-11 19:22:39 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#11120
Delete Branch "%!s()"

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?