[Snyk] Upgrade @tiptap/extension-dropcursor from 2.26.1 to 2.27.0

[sestinj]

Snyk has created this PR to upgrade @tiptap/extension-dropcursor from 2.26.1 to 2.27.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 4 versions ahead of your current version.

• The recommended version was released 21 days ago.

Issues fixed by the recommended upgrade:

	Issue	Score	Exploit Maturity
	Prototype Pollution SNYK-JS-DAGRED3ES-13110069	636	Proof of Concept

Release notes

Package name: @tiptap/extension-dropcursor

• 2.27.0 - 2025-10-29
  

  v2.27.0

• 2.26.4 - 2025-10-23
• 2.26.3 - 2025-10-09
• 2.26.2 - 2025-09-23
• 2.26.1 - 2025-07-11

from @tiptap/extension-dropcursor GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.
• Max score is 1000. Note that the real score may have changed since the PR was raised.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

---

Summary by cubic

Upgrade @tiptap/extension-dropcursor to 2.27.0 to keep the editor dependencies current and address a transitive Prototype Pollution vulnerability flagged by Snyk.

• Dependencies
  • gui/package.json: bump @tiptap/extension-dropcursor from 2.26.1 to 2.27.0.
  • No app code changes. Please sanity-check the drop cursor behavior in the editor.

^{Written for commit 5ccb72d. Summary will update automatically on new commits.}

[github-actions]

⚠️ PR Title Format

Your PR title doesn't follow the conventional commit format, but this won't block your PR from being merged. We recommend using this format for better project organization.

Expected Format:

<type>[optional scope]: <description>

Examples:

• feat: add changelog generation support
• fix: resolve login redirect issue
• docs: update README with new instructions
• chore: update dependencies

Valid Types:

feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert

This helps with:

• 📝 Automatic changelog generation
• 🚀 Automated semantic versioning
• 📊 Better project history tracking

This is a non-blocking warning - your PR can still be merged without fixing this.

[github-actions]

✅ Review Complete

Code Review Summary

⚠️ Continue configuration error. Please verify that the assistant exists in Continue Hub.

---

[cubic-dev-ai]

No issues found across 1 file