You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
run reports now carry provider, outcome_type (aborted, disconnected, length, content_filter), error_code and error, message_id, first_token_ms, duration_ms, a finish_reason per step from useCloudChat and trace_id, plus environment, release and tags from the telemetry config; one createRunReport builder in assistant-cloud assembles the body for the assistant-ui runtime and for @assistant-ui/cloud-ai-sdk, and provider_type and metadata stay on the wire for older self hosted clouds
assistant-cloud/telemetry (server side): createAssistantCloudTraceExporter, createAssistantCloudSpanProcessor, assistantCloudTraceMetadata and withAssistantCloudTraceMetadata send AI SDK GenAI spans to POST /v1/traces and hand the trace id to the browser, so a client report and its server spans merge into one run; the OpenTelemetry packages are optional peers of the subpath only
engagement events: sends, edits, stops, regenerates, copies, branch switches, suggestions, attachments, thread switches, speech, voice and shown errors are batched to POST /v1/events without any message content; telemetry.events: false opts out
cloud.scores.create for custom scores, and message feedback through useCloudChat().feedback next to the assistant-ui FeedbackAdapter
cloud.files.generatePresignedDownloadUrl and the object key on upload responses
CloudAPIError.code and details, including plan_limit_reached on a 402
@assistant-ui/core requires assistant-cloud@^0.2.0, and its store emits the composer, message and thread events the engagement reporter reads
#6987b8c5e68 - fix: compare arrays with indexed loops so sparse-array holes cannot read as equal; a sparse suggestions list now compacts to a dense one before it reaches the per-suggestion lookup (@Kinfe123)
#696198010f1 - fix: notify controlled and uncontrolled modal owners when a run opens a closed modal (@ephraimduncan)
#684324a288e - feat(cloud): claim anonymous threads into a signed-in workspace by exposing the browser's anonymous refresh token and moving its threads into an authenticated Assistant Cloud workspace after sign-in. (@okisdev)
run reports now carry provider, outcome_type (aborted, disconnected, length, content_filter), error_code and error, message_id, first_token_ms, duration_ms, a finish_reason per step from useCloudChat and trace_id, plus environment, release and tags from the telemetry config; one createRunReport builder in assistant-cloud assembles the body for the assistant-ui runtime and for @assistant-ui/cloud-ai-sdk, and provider_type and metadata stay on the wire for older self hosted clouds
assistant-cloud/telemetry (server side): createAssistantCloudTraceExporter, createAssistantCloudSpanProcessor, assistantCloudTraceMetadata and withAssistantCloudTraceMetadata send AI SDK GenAI spans to POST /v1/traces and hand the trace id to the browser, so a client report and its server spans merge into one run; the OpenTelemetry packages are optional peers of the subpath only
engagement events: sends, edits, stops, regenerates, copies, branch switches, suggestions, attachments, thread switches, speech, voice and shown errors are batched to POST /v1/events without any message content; telemetry.events: false opts out
cloud.scores.create for custom scores, and message feedback through useCloudChat().feedback next to the assistant-ui FeedbackAdapter
cloud.files.generatePresignedDownloadUrl and the object key on upload responses
CloudAPIError.code and details, including plan_limit_reached on a 402
@assistant-ui/core requires assistant-cloud@^0.2.0, and its store emits the composer, message and thread events the engagement reporter reads
#6987b8c5e68 - fix: compare arrays with indexed loops so sparse-array holes cannot read as equal; a sparse suggestions list now compacts to a dense one before it reaches the per-suggestion lookup (@Kinfe123)
#696198010f1 - fix: notify controlled and uncontrolled modal owners when a run opens a closed modal (@ephraimduncan)
#684324a288e - feat(cloud): claim anonymous threads into a signed-in workspace by exposing the browser's anonymous refresh token and moving its threads into an authenticated Assistant Cloud workspace after sign-in. (@okisdev)
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)
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
The @assistant-ui/react patch update is technically safe to accept: repository usage is limited to the documented React runtime APIs, and the release primarily contains rendering, cancellation, modal, message-part, and related fixes. CI is still running and the required approval is absent, so the recommendation is technically positive but not mechanically ready.
Key findings
Update:@assistant-ui/react0.15.18 → 0.15.19, represented by a lockfile-only change (PR diff).
Upstream compatibility:0.15.19 is a patch release. Relevant fixes include honoring explicit message-part render components and preventing queued live-completion requests after unmount (upstream changelog, render fix).
Direct usage: The repository imports @assistant-ui/react from cookbooks/app-react-ai for useLocalRuntime, AssistantRuntimeProvider, primitives, and message rendering (usage, runtime adapter).
The upstream release also contains Assistant Cloud 0.2 behavior and optional telemetry functionality, but this repository’s call site uses useLocalRuntime and does not use the cloud runtime. That means those features are not exercised by the current call sites; lack of an explicit opt-out is not treated as proof that upstream defaults are globally inactive.
No unresolved review threads or prior approval are present (reviews, comments).
No failed checks are currently reported. Auto-Label PRs passed, CodeQL is neutral, and Code quality, build, unit, Playwright, and research checks remain in progress (check runs).
The completed checks only validate repository automation and CodeQL status so far; they do not yet provide completed build, unit, or browser integration evidence. Runtime coverage remains limited because the changed cookbook path is not a full Assistant Cloud integration test.
Repository impact
The dependency is declared as a cookbook devDependency with the existing compatible range ^0.15.0; only the resolved lockfile version changes (manifest).
Under repository policy, a changeset is not required for this lockfile-only update because no published package manifest changed (Dependabot rules).
The branch is mergeable but blocked, is current with main (behind_by: 0), and is one commit ahead (PR metadata, compare API).
Repository rules require squash merging, one approving review, resolved review threads, and successful applicable quality gates (main ruleset).
Merge path
Let the pending Code quality, Build affected packages, Unit tests, Playwright, and research checks complete successfully.
Obtain the required approving review and ensure review-thread requirements remain satisfied.
Squash-merge the PR; no changeset or rebase is required at the current behind_by: 0 freshness.
Optional hardening: manually exercise the app-react-ai cookbook’s render and abort flows, since CI does not yet provide completed Assistant UI runtime integration evidence.
This workflow can rebase the branch and add required dependency changesets if repository state changes, but a maintainer must still decide whether to merge.
Generated by Fusion AI using the repository dependency-review skill.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
🤖 AI researchedDependency research completed by the Fusion AI workflow🚧 choremaintaines work, (update deps, workflos ...)dependenciesPull requests that update a dependency filejavascriptPull requests that update Javascript code
0 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps @assistant-ui/react from 0.15.18 to 0.15.19.
Release notes
Sourced from @assistant-ui/react's releases.
... (truncated)
Changelog
Sourced from @assistant-ui/react's changelog.
... (truncated)
Commits
af74661chore: update versions (#6816)6a3e11bfix(react): finish sandbox teardown after cleanup errors (#7186)3257a47fix(react): stop disposed MCP App bridge activity (#7177)e7a2ad0fix(react): detect equal-length message activity (#7159)94c3fd5fix(react): cancel WebMCP tools during async validation (#7121)bb099f6refactor(react): compose render elements through one shared helper (#7036)03fe35bfix(react): merge WebMCP abort signals without AbortSignal.any (#7014)9247ae3fix(react): honor message text render with component (#6971)91689abchore: update dependencies (#6993)b8c5e68fix: compare arrays with indexed loops in the remaining comparators (#6987)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)