chore: bump @cloudflare/ai-chat from 0.9.4 to 0.10.1 in /client

[dependabot]

Bumps @cloudflare/ai-chat from 0.9.4 to 0.10.1.

Release notes

Sourced from @​cloudflare/ai-chat's releases.

@​cloudflare/ai-chat@​0.10.1

Patch Changes

• #1982 e983026 Thanks @​mattzcarey! - Fix AI SDK v7 telemetry, which produced spans with no token counts, no finish reason, no tool results and zero durations.

  Spans that must not outlive their invocation now close at the end of it rather than at the first await. Closing at the handoff ended every WebSocket-turn span before its result existed, so every finish-time attribute was dropped. A span still open when its invocation ends is closed and marked cloudflare.agents.span.truncated instead of passing as complete, approval spans decided asynchronously included. A chat turn owns its own boundary rather than its caller's, so a turn that is not awaited — an ack-and-return submit, or an auto-continuation fired from a timer — is no longer cut short by the handler that started it. generateText is bounded on the same terms as streamText, and a turn that fails or is cancelled keeps the usage it already reported.

  chat and execute_tool spans sit under their invoke_agent operation span on v7, where they were previously emitted as unrelated roots, and tool_approval segments sit under execute_tool.

  v7 has no telemetry metadata bag, so identity and turn context arrive through runtimeContext and telemetry.includeRuntimeContext. Reserved keys project onto the attributes v6 already emits, so a query written against v6 traces still matches v7 ones; other included keys pass through as cloudflare.agents.runtime_context.{key}, and context the caller did not mark stays off the span.

@​cloudflare/ai-chat@​0.10.0

Minor Changes

• #1922 cb4c1c7 Thanks @​cjol! - Support both AI SDK v6 and v7.

  The ai peer range is ai@^6 || ^7 (and @ai-sdk/react is @^3 || ^4) across agents, @cloudflare/ai-chat, @cloudflare/codemode, and @cloudflare/think. Consumers can adopt AI SDK v7 or stay on v6 — no forced AI SDK upgrade when bumping these packages.

  Only the current implementations are covered. New optimisations and APIs made available by AI SDK v7 (broader result-shape audits, stream helper migrations, etc.) are intentionally out of scope.

  How dual-version support works — @cloudflare/think calls the AI SDK through the option names present in both majors (v7 keeps the v6 names as aliases), and normalizes the genuine divergences at the boundary:

  • Uses stepCountIs, system, experimental_telemetry, onStepFinish, and experimental_onToolCallFinish (in v7 this alias resolves to onToolExecutionEnd and fires once).

  • The tool-execution-finished event is normalized across majors: v6's { success, output, error, durationMs, stepNumber } and v7's { toolOutput, toolExecutionMs } collapse to one ToolCallResultContext. stepNumber is undefined under v7 (the v7 event no longer provides it).

  • The UI message stream is built via the result's toUIMessageStream() method (present in both majors); the standalone toUIMessageStream({ stream }) helper and result.stream are v7-only.

  • The workspace read tool emits { type: "file-data", data, mediaType, filename } model output, accepted by both majors (v7's newer { type: "file", data: { type: "data", data } } shape does not exist in v6).

    Public API notes:

  • @cloudflare/think keeps system, onStepFinish, and experimental_telemetry where callers already use them, and also accepts TurnConfig.telemetry

... (truncated)

Changelog

Sourced from @​cloudflare/ai-chat's changelog.

0.10.1

Patch Changes

• #1982 e983026 Thanks @​mattzcarey! - Fix AI SDK v7 telemetry, which produced spans with no token counts, no finish reason, no tool results and zero durations.

  Spans that must not outlive their invocation now close at the end of it rather than at the first await. Closing at the handoff ended every WebSocket-turn span before its result existed, so every finish-time attribute was dropped. A span still open when its invocation ends is closed and marked cloudflare.agents.span.truncated instead of passing as complete, approval spans decided asynchronously included. A chat turn owns its own boundary rather than its caller's, so a turn that is not awaited — an ack-and-return submit, or an auto-continuation fired from a timer — is no longer cut short by the handler that started it. generateText is bounded on the same terms as streamText, and a turn that fails or is cancelled keeps the usage it already reported.

  chat and execute_tool spans sit under their invoke_agent operation span on v7, where they were previously emitted as unrelated roots, and tool_approval segments sit under execute_tool.

  v7 has no telemetry metadata bag, so identity and turn context arrive through runtimeContext and telemetry.includeRuntimeContext. Reserved keys project onto the attributes v6 already emits, so a query written against v6 traces still matches v7 ones; other included keys pass through as cloudflare.agents.runtime_context.{key}, and context the caller did not mark stays off the span.

0.10.0

Minor Changes

• #1922 cb4c1c7 Thanks @​cjol! - Support both AI SDK v6 and v7.

  The ai peer range is ai@^6 || ^7 (and @ai-sdk/react is @^3 || ^4) across agents, @cloudflare/ai-chat, @cloudflare/codemode, and @cloudflare/think. Consumers can adopt AI SDK v7 or stay on v6 — no forced AI SDK upgrade when bumping these packages.

  Only the current implementations are covered. New optimisations and APIs made available by AI SDK v7 (broader result-shape audits, stream helper migrations, etc.) are intentionally out of scope.

  How dual-version support works — @cloudflare/think calls the AI SDK through the option names present in both majors (v7 keeps the v6 names as aliases), and normalizes the genuine divergences at the boundary:

  • Uses stepCountIs, system, experimental_telemetry, onStepFinish, and experimental_onToolCallFinish (in v7 this alias resolves to onToolExecutionEnd and fires once).
  • The tool-execution-finished event is normalized across majors: v6's { success, output, error, durationMs, stepNumber } and v7's { toolOutput, toolExecutionMs } collapse to one ToolCallResultContext. stepNumber is undefined under v7 (the v7 event no longer provides it).
  • The UI message stream is built via the result's toUIMessageStream() method (present in both majors); the standalone toUIMessageStream({ stream }) helper and result.stream are v7-only.
  • The workspace read tool emits { type: "file-data", data, mediaType, filename } model output, accepted by both majors (v7's newer { type: "file", data: { type: "data", data } } shape does not exist in v6).

  Public API notes:

  • @cloudflare/think keeps system, onStepFinish, and experimental_telemetry where callers already use them, and also accepts TurnConfig.telemetry (forwarded ahead of experimental_telemetry when present).

... (truncated)

Commits

• 413011e Version Packages (#1988)
• e983026 fix(observability): preserve AI span hierarchy across WebSocket turns (#1982)
• 4a3ee29 Version Packages (#1976)
• cb4c1c7 feat: update AI SDK to v7 (#1922)
• 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.