build(deps): bump @assistant-ui/react from 0.14.14 to 0.14.24

[dependabot]

Bumps @assistant-ui/react from 0.14.14 to 0.14.24.

Release notes

Sourced from @​assistant-ui/react's releases.

@​assistant-ui/react@​0.14.23

Patch Changes

• #4426 68dfbaa - chore: mark generateId and fromThreadMessageLike as experimental (@​okisdev)

  these two utilities became public in #4414. they now carry an @deprecated JSDoc noting the API is experimental and may change without notice, matching how the other unstable public utilities (e.g. bindExternalStoreMessage) are flagged. the distribution packages (@assistant-ui/react, @assistant-ui/react-native, @assistant-ui/react-ink) re-export them, so the annotation lands in their published types too.

• Updated dependencies [68dfbaa, fe24ad6]:

  • @​assistant-ui/core@​0.2.18

@​assistant-ui/react@​0.14.22

Patch Changes

• #4414 344f737 - feat: export fromThreadMessageLike and generateId from the public API (@​okisdev)

  these two utilities were only reachable via @assistant-ui/core/internal, so materializing a ThreadMessageLike into a ThreadMessage, or generating an id for a hand-built message, meant reaching into internals (the first-party ag-ui and a2a runtimes already did). they are now exported from @assistant-ui/core, @assistant-ui/react, @assistant-ui/react-native, and @assistant-ui/react-ink. also removes the now-redundant duplicate listing of both from the unstable INTERNAL namespace (the one in-repo consumer, the with-ffmpeg example, now uses the public export).

• #4419 3cef745 - feat(react): add minCommitMs to SmoothOptions to throttle committed reveal updates (@​okisdev)

  useSmooth keeps advancing the typewriter reveal every frame, but with minCommitMs the visible text (and the downstream re-render and markdown re-parse it triggers) is committed at most once per interval. The final frame always commits, so no characters are lost. Defaults to 0, which commits every frame and preserves the previous behavior.

• #4411 d76a922 - feat: add unstable_useLiveCompletionAdapter for async trigger completions (@​okisdev)

  bridges an async completion source (a server search, a gateway RPC) into the synchronous Unstable_TriggerAdapter. search returns cached items synchronously and schedules a debounced fetch with stale-request cancellation; when results land the adapter re-creates so the popover re-renders. also adds an isLoading prop on ComposerPrimitive.Unstable_TriggerPopover (surfaced on the popover scope) so async sources can render a loading state.

• Updated dependencies [344f737, a2e21ee]:

  • @​assistant-ui/core@​0.2.17

@​assistant-ui/react-a2a@​0.2.20

Patch Changes

• #4414 344f737 - chore: import generateId and fromThreadMessageLike from the public @assistant-ui/core entry instead of /internal (@​okisdev)

  no behavior change; these utilities are now part of the public API.

• Updated dependencies [344f737, a2e21ee]:

  • @​assistant-ui/core@​0.2.17

@​assistant-ui/react-o11y@​0.0.24

Patch Changes

• Updated dependencies [8d3b0e8]:
  • @​assistant-ui/tap@​0.9.2
  • @​assistant-ui/store@​0.2.18

@​assistant-ui/react@​0.14.21

Patch Changes

• #4403 9f59d69 - fix: prevent compiled context store hooks from skipping subscriptions (@​Yonom)

... (truncated)

Changelog

Sourced from @​assistant-ui/react's changelog.

0.14.24

Patch Changes

• #4543 d0987a3 - external-store: add unstable_onBranchChange adapter callback that fires on explicit switchToBranch, emitting the canonical (persisted) head and visible message ids, deduped by head (@​AVGVSTVS96)

• #4517 cefcf27 - chore: update dependencies (@​okisdev)

• #4545 4550578 - add unstable_useComposerInput headless bridge (value/setText/send/isDisabled/canSend) and unstable_useTriggerPopoverAriaProps for building a custom composer input without ComposerPrimitive.Input (@​AVGVSTVS96)

• #4310 0c51b90 - feat: add unstable_ interactables API; restore and deprecate the previous interactables API (@​AVGVSTVS96)

  The redesigned interactables API is now available as an additive unstable_* surface for building editable, in-message UI while preserving the existing stable API for compatibility.

  • unstable_useInteractable(name, config) registers an interactable and returns its state plus methods in one hook.
  • Each unstable interactable name gets one stable update_{name} tool. When multiple instances share a name, the tool targets an instance by id.
  • Thread-scoped interactables rendered inside message parts expose version, including the state for that message, whether it is the latest tool-driven version, and restore().
  • Added unstable_interactableTool(...) for defining a creating tool and its in-message render UI together.
  • Added unstable_useInteractableVersions(id, name) for version history UIs.
  • Persistence adapters can now provide load() and be passed directly to unstable_Interactables({ persistence }).

  The previous useAssistantInteractable / useInteractableState / Interactables API remains available unchanged and is marked deprecated. Existing apps do not need to migrate immediately.

  Migration notes for the unstable API:

  - const id = useAssistantInteractable("taskBoard", config);
  - const [state, { setState }] = useInteractableState(id, initialState);
  + const [state, { id, setState }] = unstable_useInteractable("taskBoard", config);

  • Use unstable_interactables: unstable_Interactables() when registering the unstable scope.
  • unstable_useInteractableState(id) is intended for secondary readers and returns undefined until the owner registers.
  • The unstable API uses per-name update tools (update_{name}) with an id parameter instead of legacy per-instance tools (update_{name}_{id}).
  • A top-level id field in stateSchema is reserved for instance addressing. Rename domain state fields to itemId, recordId, etc. if the model should edit them.
  • Model selection should be represented as ordinary state in the unstable API; the legacy selected registration prop and setSelected method remain available on the deprecated stable API.

• #4591 f582f09 - feat: honor startRun false across staged-message-capable runtimes (@​Yonom)

• #4542 4acd4c0 - add unstable id-keyed thread message rendering APIs for virtualized and custom message lists. unstable_useThreadMessageIds() returns the thread's message ids (stable array identity across content-only updates), and ThreadPrimitive.Unstable_MessageById renders a single message by id with the same component surface as MessageByIndex. A missing or removed id renders null instead of throwing. (@​AVGVSTVS96)

• Updated dependencies [ddc40b7, ea52de0, 29c6fdb, d0987a3, cefcf27, 0c51b90, 3a8f685, ec6adf4, 4acd4c0]:

  • @​assistant-ui/core@​0.2.19
  • [email protected]
  • [email protected]
  • @​assistant-ui/store@​0.2.19
  • @​assistant-ui/tap@​0.9.3

0.14.23

... (truncated)

Commits

• See full diff in compare view

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 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)

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.