chore(deps): update dependency @liveblocks/node to v3.14.1

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@liveblocks/node (source)	3.13.0 → 3.14.1

---

Release Notes

liveblocks/liveblocks (@​liveblocks/node)

v3.14.1: 3.14.1

Compare Source

@liveblocks/react

• Fix paginated hooks (useThreads, useInboxNotifications, and useAiChats)
  stopping pagination after the first fetchMore() call when auto-paginating in
  a useEffect.

v3.14.0: 3.14 🥧

Compare Source

This release adds support for opting-in to the new storage engine on a per-room basis. The new storage engine can support larger documents, is more performant, is considered more stable, and will eventually become our default engine for all new rooms in the future.

As of this release, the default storage engine still remains engine version 1.

To give it a try, simply pass engine: 2 when entering a new room. After a room is created, you cannot change the engine it was created with anymore.

For example:

// Vanilla JS
client.enterRoom("my-new-room", { engine: 2 });

or:

// In React
<RoomProvider id="my-new-room" engine={2}>
  ...
</RoomProvider>

@liveblocks/client

• Support for selecting the preferred engine when entering new rooms: client.enterRoom("my-new-room", { engine: 2 })
• Internal protocol optimizations to support larger storage documents
• Add new config option createClient({ baseUrl: "https://..." }) to allow connecting to the Liveblocks dev server
• Improve LiveList performance when processing large batches of operations
• Improve LiveList.push() efficiency to prevent unbounded position string growth over time
• Fix crash when clearing documents with a large number of keys
• Remove the largeMessageStrategy client option. The WebSocket message limit has been increased from 1 MB to 32 MB, making this setting obsolete.

@liveblocks/react

• Support for selecting the preferred engine when entering new rooms: <RoomProvider id="my-new-room" engine={2}>...</RoomProvider>
• Add new config option <LiveblocksProvider baseUrl="https://..." /> to allow connecting to the Liveblocks dev server
• Exclude marking a thread or inbox notification as read from blocking navigation when preventUnsavedChanges is enabled.

@liveblocks/react-tiptap and @liveblocks/react-lexical

• Portaled elements now respect the portalContainer option from @liveblocks/react-ui’s LiveblocksUiConfig instead of always using document.body.

@liveblocks/zustand and @liveblocks/redux

• Support for selecting the preferred engine when entering new rooms: enterRoom("my-new-room", { engine: 2 })

@liveblocks/node

• Add new .setPresence() method to set ephemeral presence for a user in a room via the REST API, without requiring a WebSocket connection
• Deprecated tenantId parameter in client methods, use organizationId instead.

v3.13.5: 3.13.5

Compare Source

• Replace y-tiptap with y-prosemirror to prevent plugin key conflict, which was causing change source to be incorrectly set in Blocknote.

v3.13.4: 3.13.4

Compare Source

@liveblocks/react-tiptap

• Fix an issue where FloatingComposer wouldn’t auto-focus and FloatingToolbar would conflict with it.

v3.13.3: 3.13.3

Compare Source

@liveblocks/client

• Bump hardcoded client-side socket connection timeout from 10s to 20s.
• Add more detailed timing info to enableDebugLogging to better debug connection issues.

@liveblocks/react-ui

• Fix an issue where Composer and AiComposer would throw an error when mounted/unmounted.

v3.13.2: 3.13.2

Compare Source

@liveblocks/node

• Add a new alwaysUseKnowledge option when creating or updating copilots. When
  this option is enabled, the copilot retrieves and uses the uploaded knowledge
  sources on each user query. When disabled, the copilot will retrieve the
  uploaded knowledge sources only when the user query relates to the knowledge
  prompt set on the copilot.

v3.13.1: 3.13.1

Compare Source

@liveblocks/client

• Fix issue where storage subscriptions wouldn't fire after concurrent move and set operations, causing stale LiveList state in UI.

---

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 this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
job-prep	Ready	Preview, Comment	Mar 1, 2026 11:27pm

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[cubic-dev-ai]

No issues found across 1 file