Update dependency @liveblocks/client to v3.18.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@liveblocks/client (source)	3.13.0 → 3.18.3

---

Release Notes

liveblocks/liveblocks (@​liveblocks/client)

v3.18.3: 3.18.3

Compare Source

@liveblocks/*

• Third-party libraries like yjs, @tiptap/*, and @blocknote/* are now declared as peer dependencies instead of bundled dependencies across all packages that use them.

v3.18.2: 3.18.2

Compare Source

@liveblocks/client

• New experimental room.history.disable(fn) API that allows running storage mutations without them appearing on the undo/redo stacks. Intended for background/async writes (e.g. writing back AI generation results) that should not be undoable.
• Fix ToJson type losing specific value types for Record<string, T> fields in Storage

v3.18.1: 3.18.1

Compare Source

@liveblocks/react-ui

• Mentions suggestions now appear in more cases after typing @:
  • After punctuation like !, ., (, etc. (e.g. Hello!@​,
    cc: the other team (@​)
  • After emojis (e.g. Hello 👋@​)

v3.18.0: 3.18.0

Compare Source

For full upgrade instructions, see the 3.18 upgrade guide.

@liveblocks/client

• Breaking: useStorage now returns plain objects for LiveMap values instead of Map instances. Legacy APIs have been removed: .toImmutable(), .toObject(), .toArray().
• New .toJSON() on all Live structures, returning a cached JSON-compatible snapshot. JSON.stringify(root) now just works.
• New LiveObject.from(obj) to create a LiveObject from plain JSON, recursively converting nested objects/arrays to Live structures.
• New .reconcile(obj) to efficiently reconcile a LiveObject tree to match a JSON snapshot, only mutating what changed.
• initialStorage accepts LiveObject.from() result directly.

@liveblocks/react-flow/node

• New mutateFlow() API for reading and mutating React Flow data from a Node.js backend. Install via npm i @​liveblocks/react-flow, import from @liveblocks/react-flow/node. See the docs.

@liveblocks/react-ui

• Add standalone Avatar component to complement AvatarStack for more fine-grained customization.
• Add variant prop to AvatarStack to support outlined avatars.

@liveblocks/zustand and @liveblocks/redux

• Fix: Initial storage seeding no longer creates an undo frame.
• Fix: Presence updates are now batched with storage updates.

v3.17.0: 3.17.0

Compare Source

@liveblocks/react-flow

• Introduce the package. Install with npm install @​liveblocks/react-flow.
  Provides hooks and components that add collaboration to any React Flow diagram
  using Liveblocks Storage:
  • Use the useLiveblocksFlow hook to make React Flow synced and
    collaborative.
  • Use the Cursors component to show other users' cursors inside React Flow.

@liveblocks/react-ui

• Allow customizing cursors in the Cursors component by passing a
  components={{ Cursor: MyCursor }} prop.

v3.16.0: 3.16.0

Compare Source

@liveblocks/chat-sdk-adapter

• Introduce the package. Install with
  npm install @​liveblocks/chat-sdk-adapter. Provides a
  chat-sdk-compatible backend adapter
  backed by Liveblocks Comments: webhooks, posting and editing messages,
  reactions, paginated fetches, thread and channel helpers, and optional
  resolveUsers / resolveGroupsInfo hooks.

@liveblocks/react

• Add Feeds hooks: useFeeds, useFeedMessages, useCreateFeed,
  useDeleteFeed, useUpdateFeedMetadata, useCreateFeedMessage,
  useDeleteFeedMessage, and useUpdateFeedMessage.

@liveblocks/node

• Add REST client methods for Feeds: getFeeds, getFeed, createFeed,
  updateFeed, deleteFeed, getFeedMessages, createFeedMessage,
  updateFeedMessage, and deleteFeedMessage.

Python SDK

• Add Feeds REST API support on the sync and async clients (get_feeds,
  get_feed, create_feed, update_feed, delete_feed, get_feed_messages,
  create_feed_message, update_feed_message, delete_feed_message) with
  matching request/response models.

@liveblocks/client

• Add Feeds: room-scoped feeds with metadata and messages and APIs to list,
  create, update, and delete feeds and messages (fetchFeeds,
  fetchFeedMessages, addFeed, updateFeed, deleteFeed, addFeedMessage,
  updateFeedMessage, deleteFeedMessage).

@liveblocks/react-ui

• Add body prop to Comment to allow overriding only the default rich-text
  comment body while still keeping attachments, reactions, and
  additionalContent as is, unlike when using the children prop.
• Fix AvatarStack negative margin breaking alignment.

v3.15.5: 3.15.5

Compare Source

@liveblocks/tiptap

• Improve clipboard handling when text nodes containing comments were copied or
  pasted.

Python SDK

• Fix request body for certain endpoints, like update_room_id,
  initialize_storage_document incorrectly set as optional.

v3.15.4: 3.15.4

Compare Source

@liveblocks/node

• Add Liveblocks.getAttachment() method to get an attachment's metadata and a
  presigned download URL.

Python SDK

• Add get_attachment() method to get an attachment's metadata and a presigned
  download URL.

v3.15.3: 3.15.3

Compare Source

Python SDK

• Introduce the Python package. Install with pip install liveblocks. Provides
  sync and async clients for the full Liveblocks API (rooms, storage, threads,
  comments, etc.) for backend use.

@liveblocks/react-ui

• Add showSubscription prop to Thread to control whether to show the
  thread’s subscription status.

v3.15.2: 3.15.2

Compare Source

@liveblocks/client

• Deprecate the engine option on enterRoom(). This flag no longer has any effect.

@liveblocks/react

• Deprecate the engine prop on RoomProvider. This flag no longer has any effect.

@liveblocks/node

• Deprecate the engine option on createRoom(). This flag no longer has any effect.
• Stop sending the engine field in the room creation request body.

v3.15.1: 3.15.1

Compare Source

@liveblocks/react-ui

• Add gap prop to AvatarStack to control the --lb-avatar-stack-gap CSS
  variable.
• Add padding prop to CommentPin to control the --lb-comment-pin-padding
  CSS variable.
• Fix size props on AvatarStack and CommentPin not working as expected
  when passing numbers.
• Fix autoFocus prop on FloatingComposer.
• Improve avatars’ ordering and max logic in AvatarStack.
• Support children prop on CommentPin.

v3.15.0: 3.15.0

Compare Source

@liveblocks/react-ui

• Add various new ways to customize Thread and Comment:
  • Comments in Thread can now be overridden or customized via the
    components prop.
  • New parts of Comment (content, avatar, author, and date) can now be
    overridden or customized via the children, additionalContent, avatar,
    author, and date props.
• Fix commentDropdownItems prop on Thread not working as expected in some
  cases.

@liveblocks/react

• Each createRoomContext() invocation now creates its own isolated context to
  allow nesting independent room contexts and their RoomProvider components.

@liveblocks/react-blocknote

• Support newer BlockNote versions and bump the minimum required version to
  v0.43.0. (Thanks @​nperez0111 for the contribution!)

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

• Improve how inline components passed to components={{ ... }} props are
  handled by keeping them stable instead of re-mounting them on every render.
• Move @radix-ui/* dependencies to the radix-ui mono package.

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: (UTC)

• 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	Apr 19, 2026 6:01am

[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

[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