Skip to content

chore(deps): bump the assistant-ui group across 1 directory with 2 updates - #5172

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/assistant-ui-d09cd95d70
Open

chore(deps): bump the assistant-ui group across 1 directory with 2 updates#5172
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/assistant-ui-d09cd95d70

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 12, 2026

Copy link
Copy Markdown
Contributor

Bumps the assistant-ui group with 2 updates in the / directory: @assistant-ui/react-ai-sdk and @assistant-ui/react.

Updates @assistant-ui/react-ai-sdk from 1.4.1 to 1.4.4

Changelog

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

1.4.4

Patch Changes

  • #5441 c7ff5aa - fix(react-ai-sdk): forward audio message parts as file parts instead of throwing (@​okisdev)

  • #5452 9579a63 - fix: wrap bare base64 file and image payloads in a data URL envelope (@​okisdev)

    convertToModelMessages passes a file part's url to an unguarded new URL(), so a FileMessagePart or ImageMessagePart whose payload is raw base64 rather than a data URL or an http source rejected with Invalid URL. Both branches now wrap a non-URL payload using the part's own media type; data URLs and http sources are still forwarded untouched.

  • #5336 9f12130 - feat: resume stream ids discovered after the chat runtime mounts (@​Kinfe123)

  • #5466 2b24bd4 - fix: detect the media type of a bare base64 image instead of assuming png (@​okisdev)

    getImageMediaType resolved an explicit contentType, then a data URL envelope, then fell back to image/png. An ImageMessagePart carrying raw base64 has neither, so JPEG, GIF and WebP payloads were all announced to the provider as png. The leading bytes are now read with detectMediaType from @ai-sdk/provider-utils, the same helper the AI SDK uses internally, and image/png remains the fallback when no signature matches.

    The sniff only runs on a payload that is not a parsable url, and never propagates a throw: detectMediaType raises on input that is not valid base64.

  • #5459 22b05a4 - fix: wrap a file part payload that is not a parsable url (@​okisdev)

    getPromptParts put FileMessagePart.data straight into the OpenCode file part's url. OpenCode forwards that into an AI SDK file part (sst/opencode, session/message-v2.ts), whose url reaches an unguarded new URL(), so a payload that is raw base64 rather than a data URL or an http source failed there. A non-parsable payload is now wrapped in a data:<mime>;base64, envelope; data URLs and http sources are forwarded untouched, and a sourceType: "id" reference is left alone so it fails loudly instead of shipping a corrupt payload.

    The predicate behind that decision moves to isParsableUrl in @assistant-ui/core/internal, next to the httpUrlPattern and parseDataUrl it belongs with, and react-ai-sdk now imports it instead of keeping its own copy. No behavior change there.

  • #5337 bb5a0d9 - fix: pass null-body-status responses through the resumable fetch wrapper instead of reconstructing them, avoiding a TypeError on WebKit when a 204/205/304 carries a non-null empty body (@​rupic-app)

  • #5332 d610323 - feat: allow the resumable stream id storage key to be derived lazily from a getter, so apps can scope it per thread (see the Resumable Streams guide) (@​rupic-app)

  • #5479 011e275 - fix: read an image's media type from its leading bytes in both adapters (@​okisdev)

    detectImageMediaType and dataUrlMediaType join parseDataUrl and isParsableUrl in @assistant-ui/core/internal. An ImageMessagePart carries no media type, so an adapter that must declare one on the wire now reads it from the payload rather than assuming a format. It never throws, whatever a caller put on the part.

    react-ai-sdk and react-opencode run the same ladder rung for rung: the attachment's contentType, then a data URL's declared type when that is itself an image type (read whether or not the payload is base64, so an SVG data URL keeps its type), then the leading bytes, then image/png. Previously react-opencode had no byte rung at all, and react-ai-sdk's was skipped for any data: payload, so a JPEG inside a generic application/octet-stream envelope resolved to png on both.

    Resolving the label alone was not enough, because a data URL's own media type wins over the declared one downstream. Both adapters now rebuild the envelope when it disagrees with the resolved type and forward it untouched when it agrees. That applies to file parts too, where a mimeType: "application/pdf" part carrying an application/octet-stream envelope was announced as pdf and delivered as octet-stream. File parts also gain the same three rungs, so an empty mimeType falls to the envelope and then to application/octet-stream rather than producing a malformed data:;base64, url; vercelAttachmentAdapter emits exactly that shape for a file the OS cannot type.

  • #5485 da32fe0 - refactor: share the media type ladder and wire url between adapters (@​okisdev)

    resolveImageMediaType, resolveFileMediaType and toMediaWireUrl join the data URL helpers in @assistant-ui/core/internal. react-ai-sdk and react-opencode had arrived at identical ladders and an identical wire url builder by construction rather than by sharing code, and they had already drifted apart twice while getting there. Both now call the shared functions and keep only their own part-shape plumbing.

    No behavior change: both adapters' existing suites pass untouched.

  • Updated dependencies [b19c2f5, 01140bd, 8c99934, ece5a54, 2fdff87, 90b3003, 4c313cf, 55b2824, 22b05a4, f913c21, c868710, 011e275, da32fe0, f913c21, 5bb2573, 5ececc1]:

    • @​assistant-ui/core@​0.3.4
    • assistant-stream@0.3.32
    • @​assistant-ui/store@​0.3.3

1.4.3

Patch Changes

... (truncated)

Commits
  • c67168e chore: update versions (#5429)
  • 9f12130 feat(react-ai-sdk): support resumable storage updates (#5336)
  • d610323 fix(react-ai-sdk): scope resumable stream id storage key per thread (#5332)
  • bb5a0d9 fix(react-ai-sdk): pass null-body-status responses through the resumable fetc...
  • da32fe0 refactor(core): share the media type ladder and wire url between adapters (#5...
  • 011e275 fix(react-ai-sdk,react-opencode): converge the image media type ladder (#5479)
  • 2b24bd4 fix(react-ai-sdk): detect the media type of a bare base64 image (#5466)
  • 22b05a4 fix(react-opencode): wrap a file payload that is not a parsable url (#5459)
  • 9579a63 fix(react-ai-sdk): wrap bare base64 file and image payloads in a data url (#5...
  • c7ff5aa fix(react-ai-sdk,eve): forward audio parts instead of throwing (#5441)
  • Additional commits viewable in compare view

Updates @assistant-ui/react from 0.15.0 to 0.15.4

Release notes

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

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

Patch Changes

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

Patch Changes

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

Patch Changes

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

Patch Changes

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

Patch Changes

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

Patch Changes

  • #5430 dcacd9b - feat: AuiProvider extends/config grammar. config={AuiConfig({...})} alone creates a top-level root client; nested providers must pass extends — a client to extend, or null to isolate (dev-enforced). An empty config creates a client extending the extends client; ref exposes the resulting client. The config prop only accepts configs built with AuiConfig(...) (branded type). AssistantRuntimeProvider gains an optional config prop whose scopes are provided alongside the runtime scope. The useAui({...}) extension overload and the AuiProvider value prop are deprecated; value={client} now exposes a client extending the given one (same scopes, new identity) rather than the exact instance. useAui({}) with an empty scope object now mounts a rooted host (so the scope set can grow across renders) instead of a passthrough derived-only client. useAuiState state enumeration (Object.keys/spread) now includes scopes inherited from parent clients, matching in-operator behavior. Clients derived from a hand-built parent (a plain object with subscribe/on) forward scoped on(...) listeners to the parent's on instead of throwing for scopes the parent does not expose. (@​Yonom)

  • #5605 afb59f2 - fix: prevent cyclic span parent links from crashing observability trees (@​Kinfe123)

  • Updated dependencies [dcacd9b, aa302ee, aa302ee, 71cf74e]:

    • @​assistant-ui/store@​0.3.4

... (truncated)

Changelog

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

0.15.4

Patch Changes

  • #5566 7528465 - fix: skip add-message commands with no supported parts in assistant transport runtime (@​Yonom)

  • #5565 78943a3 - feat: add opt-in strict: false mode that reconciles malformed stream input instead of throwing (decoders, state accumulator); assistant-transport resume runs always decode leniently (@​Yonom)

  • Updated dependencies [7f7f8a2, 6c062f1, 78943a3]:

    • @​assistant-ui/core@​0.3.5
    • assistant-cloud@0.1.38
    • assistant-stream@0.3.33

0.15.3

Patch Changes

  • #5432 8ca9930 - fix: refresh MCP App resources when the host changes (@​Kinfe123)

    Custom McpAppsHost resources must now return a stable object identity (for example, with useMemo); an unstable host keeps the widget in loadingFallback and refetches on every re-render.

  • #5447 8c99934 - docs: deprecate Unstable_AudioMessagePart in favour of file parts (@​okisdev)

    Audio belongs on a file part with an audio/* mime type. file is a member of both the user and assistant unions and carries a filename, neither of which the audio part can express. The payload form a file part needs is still adapter specific; the message primitive docs enumerate it. The audio part and the Unstable_Audio slot stay honored everywhere they are accepted and will not gain fields.

  • #5439 ece5a54 - feat: sourceType opt-in on file message parts so attachment adapters can send url/id file references (@​ShobhitPatra)

  • #5542 55b2824 - feat: expose threadListItem.isRunning so a thread list row can show its own run (@​okisdev)

    a thread list row had no supported way to tell whether its thread was running: thread.isRunning describes the open thread, and the item state carried no run state at all, so a run continuing on a thread the user had switched away from was invisible.

    threadListItem.isRunning now reports it, and stays true for a background run. runtimes that keep background threads alive answer it through the new optional ThreadListRuntimeCore.unstable_isThreadRunning; the rest report the open thread's run state, which they already track.

    InMemoryThreadList also renames threads for real instead of dropping the new title.

  • #5537 c868710 - fix: keep a settled tool call distinguishable from an unfinished one, so a tool returning false, 0, "" or null no longer loses its result on the cloud round trip and no longer reads as never completed (@​okisdev)

  • #5522 f913c21 - feat: add threads.reloadMainThread() to refetch the open thread's remote state in place (@​taoche)

  • #5417 5bb2573 - fix: suggestion trigger with send no longer overwrites the composer draft while a run is in progress; on runtimes without queue support it now renders disabled mid-run, matching ComposerPrimitive.Send (@​ephraimduncan)

  • Updated dependencies [b19c2f5, 01140bd, 8c99934, ece5a54, 2fdff87, 90b3003, 4c313cf, 55b2824, 22b05a4, f913c21, c868710, 011e275, da32fe0, f913c21, 5bb2573, 71231d3, 5ececc1]:

    • @​assistant-ui/core@​0.3.4
    • assistant-stream@0.3.32
    • @​assistant-ui/store@​0.3.3
    • safe-content-frame@0.0.26

0.15.2

... (truncated)

Commits
  • d54dfe1 chore: update versions (#5554)
  • 7528465 fix(react): skip add-message commands with no supported parts (#5566)
  • 78943a3 feat(assistant-stream): add opt-in strict=false lenient decoding mode (#5565)
  • c67168e chore: update versions (#5429)
  • 55b2824 feat(core,react,ui): per-thread run state and thread list rename (#5542)
  • c868710 fix: keep a settled tool call distinguishable from an unfinished one (#5537)
  • f913c21 feat(core): add the in-place refetch contract behind threads.reloadMainThread...
  • 5bb2573 fix(core,react): preserve composer draft when suggestion send fires mid-run (...
  • 8ca9930 fix(react): refresh mcp app resources after host changes (#5432)
  • 8c99934 docs(core,react): deprecate Unstable_AudioMessagePart in favour of file parts...
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 12, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner August 12, 2026 05:37
@dependabot dependabot Bot added the javascript Pull requests that update javascript code label Aug 12, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner August 12, 2026 05:37
@changeset-bot

changeset-bot Bot commented Aug 12, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: d7c2ac3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

…dates

Bumps the assistant-ui group with 2 updates in the / directory: [@assistant-ui/react-ai-sdk](https://github.com/assistant-ui/assistant-ui/tree/HEAD/packages/react-ai-sdk) and [@assistant-ui/react](https://github.com/assistant-ui/assistant-ui/tree/HEAD/packages/react).


Updates `@assistant-ui/react-ai-sdk` from 1.4.1 to 1.4.4
- [Release notes](https://github.com/assistant-ui/assistant-ui/releases)
- [Changelog](https://github.com/assistant-ui/assistant-ui/blob/main/packages/react-ai-sdk/CHANGELOG.md)
- [Commits](https://github.com/assistant-ui/assistant-ui/commits/@assistant-ui/react-ai-sdk@1.4.4/packages/react-ai-sdk)

Updates `@assistant-ui/react` from 0.15.0 to 0.15.4
- [Release notes](https://github.com/assistant-ui/assistant-ui/releases)
- [Changelog](https://github.com/assistant-ui/assistant-ui/blob/main/packages/react/CHANGELOG.md)
- [Commits](https://github.com/assistant-ui/assistant-ui/commits/@assistant-ui/react@0.15.4/packages/react)

---
updated-dependencies:
- dependency-name: "@assistant-ui/react"
  dependency-version: 0.15.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: assistant-ui
- dependency-name: "@assistant-ui/react-ai-sdk"
  dependency-version: 1.4.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: assistant-ui
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(deps): bump the assistant-ui group with 2 updates chore(deps): bump the assistant-ui group across 1 directory with 2 updates Aug 12, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/assistant-ui-d09cd95d70 branch from 02758bf to d7c2ac3 Compare August 12, 2026 23:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants