fix(deps): update tiptap monorepo to v3.4.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@tiptap/extension-blockquote (source)	3.3.1 -> 3.4.1
@tiptap/extension-bold (source)	3.3.1 -> 3.4.1
@tiptap/extension-bullet-list (source)	3.3.1 -> 3.4.1
@tiptap/extension-code (source)	3.3.1 -> 3.4.1
@tiptap/extension-code-block (source)	3.3.1 -> 3.4.1
@tiptap/extension-link (source)	3.3.1 -> 3.4.1
@tiptap/extension-list-item (source)	3.3.1 -> 3.4.1
@tiptap/extension-ordered-list (source)	3.3.1 -> 3.4.1
@tiptap/extension-placeholder (source)	3.3.1 -> 3.4.1
@tiptap/extension-strike (source)	3.3.1 -> 3.4.1
@tiptap/extension-underline (source)	3.3.1 -> 3.4.1
@tiptap/react (source)	3.3.1 -> 3.4.1
@tiptap/starter-kit (source)	3.3.1 -> 3.4.1

---

Release Notes

ueberdosis/tiptap (@​tiptap/extension-blockquote)

v3.4.1

Compare Source

Releases

@​tiptap/extension-text-style@​3.4.1

Patch Changes

• 46fa8b8: Prefer the raw inline style attribute when parsing color and
  background-color so the original format (hex, rgba/hsla, etc.) is
  preserved instead of falling back to the computed element.style.*
  value (which often resolves to rgb(...)).

  This fixes mismatches where consumers (for example, demo toolbars and
  color pickers) expected the original hex values when initializing the
  editor from HTML.

  • The color and background-color parsers now look for a style
    attribute first and extract the declared value. If no raw style is
    present, they still fall back to element.style.color /
    element.style.backgroundColor.

  MIGRATION NOTES

  • This is a patch-level change. It corrects parsing behavior and is the
    least-disruptive fix for the issue.
  • If your code relied on the parser returning computed rgb(...)
    strings, you may see different string values (for example #​958DF1
    instead of rgb(149, 141, 241)) when HTML contained hex values.
  • If you need a stable, normalized format for comparisons, normalize the
    attribute (for example with a color utility like tinycolor2) before
    comparing or use the editor APIs in a way that doesn't depend on the
    exact string representation.
  • @​tiptap/core@​3.4.1

@​tiptap/react@​3.4.1

Patch Changes

• 4dd8d58: fix: @​types/react version mismatch

@​tiptap/suggestion@​3.4.1

Patch Changes

• 59fb86f: Previously, clientRect was only obtained through decorationNode. If decorationNode could not be obtained, clientRect was set to null, which caused the suggestion not to render in some IME scenarios (notably Chinese IME).

  This change adds a fallback method to compute clientRect from the editor's cursor position when decorationNode is not available. It generates a DOMRect based on the cursor coordinates so the suggestion can render even when the decoration node is missing.

v3.4.0

Compare Source

Patch Changes

• Updated dependencies [895c73f]
• Updated dependencies [ad51daa]
  • @​tiptap/core@​3.4.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud