Skip to content

ci: Version Packages - #2082

Merged
AlemTuzlak merged 1 commit into
mainfrom
changeset-release/main
Nov 9, 2026
Merged

AlemTuzlak merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@tanstack/ai@1.3.0

Minor Changes

  • #2071 e8546f9 - A run that the agent loop stops before the model finished now says so. When agentLoopStrategy (for example maxIterations) or a middleware onShouldContinue returns false while tool results wait for the next model call, chat() ends the stream with a RUN_FINISHED that has metadata.tanstack.loopStopped: true, and the last stored assistant message gets the same field. finishReason stays the reason of the last model call (tool_calls, or length for a cut answer). A run that the model ends has no loopStopped.

    In @tanstack/ai-harness, a turn that the loop stops settles with { outcome: 'completed', loopStopped: true }. session.settled(), the harness.input.settled event of createHarnessClient().events(), and the transcript all carry it.

  • #2087 5fd5355 - Keep Responses item ids and phases when adjacent answer text is merged. Save each item's text length so replay can restore its boundary.

Patch Changes

  • #2056 9393839 - @tanstack/ai exports stableJson: JSON text with the keys of every object in sorted order, for values that come back from a store with their keys reordered. @tanstack/ai-harness now imports it and no longer keeps its own copy.

  • #2086 215e339 - Stop a long-running server tool from leaking memory. While a tool ran, the event poll subscribed to the tool's promise again every 10 ms and kept every subscription until the tool finished. Memory grew by about 100 MB per hour while a tool stayed pending. The poll now subscribes once.

  • #2069 7157ef3 - Preserve metadata from live AG-UI TOOL_CALL_RESULT events on ToolResultPart.

@tanstack/ai-harness@0.3.0

Minor Changes

  • #2071 e8546f9 - A run that the agent loop stops before the model finished now says so. When agentLoopStrategy (for example maxIterations) or a middleware onShouldContinue returns false while tool results wait for the next model call, chat() ends the stream with a RUN_FINISHED that has metadata.tanstack.loopStopped: true, and the last stored assistant message gets the same field. finishReason stays the reason of the last model call (tool_calls, or length for a cut answer). A run that the model ends has no loopStopped.

    In @tanstack/ai-harness, a turn that the loop stops settles with { outcome: 'completed', loopStopped: true }. session.settled(), the harness.input.settled event of createHarnessClient().events(), and the transcript all carry it.

Patch Changes

  • #2056 9393839 - @tanstack/ai exports stableJson: JSON text with the keys of every object in sorted order, for values that come back from a store with their keys reordered. @tanstack/ai-harness now imports it and no longer keeps its own copy.

  • Updated dependencies [e8546f9, 5fd5355, 9393839, 215e339, 7157ef3]:

    • @tanstack/ai@1.3.0
    • @tanstack/ai-persistence@1.0.1

@tanstack/ai-acp@1.0.2

Patch Changes

@tanstack/ai-bedrock@1.2.1

Patch Changes

  • #2057 844496a - A Bedrock Converse chat stream that ends with stopReason: 'guardrail_intervened' now reports finishReason: 'content_filter' on RUN_FINISHED. Before, it was a normal stop. The structured-output stream uses the same finish reason when the body is valid JSON. When a guardrail leaves no JSON, that stream reports RUN_ERROR with code content_filter instead of empty-response or parse-error.

  • Updated dependencies [e8546f9, 5fd5355, 9393839, 215e339, 7157ef3]:

    • @tanstack/ai@1.3.0
    • @tanstack/openai-base@1.0.3

@tanstack/ai-code-mode@1.1.1

Patch Changes

@tanstack/ai-compaction@1.0.1

Patch Changes

  • #2056 9393839 - A compaction checkpoint is now reused when the message store gives messages back with their object keys in another order, as PostgreSQL jsonb and schema parsing do. hashMessages hashes the messages with stableJson, so an equal history no longer looks changed and the summarizer does not run again over it. After the upgrade, saved checkpoints, saved usage counts and ready background summaries whose messages were not stored in sorted key order miss until the next compaction replaces them. Each such thread pays for one summarizer run.

  • Updated dependencies [e8546f9, 5fd5355, 9393839, 215e339, 7157ef3]:

    • @tanstack/ai@1.3.0

@tanstack/ai-computer-use@1.1.1

Patch Changes

@tanstack/ai-gemini@1.2.1

Patch Changes

  • #2083 548ec42 - Gemini Live (realtime) usage events now include thoughtsTokenCount in completionTokens, matching how the text adapters report usage.

  • #2053 925a505 - Send a multimodal tool result's parts to Gemini once, inside its functionResponse. Before, the adapter also put them beside the functionResponse in the same turn, so each image was sent and billed twice.

  • #2088 9bcdd41 - Report Gemini content filter stops (SAFETY, RECITATION, BLOCKLIST, PROHIBITED_CONTENT, SPII, IMAGE_SAFETY, IMAGE_PROHIBITED_CONTENT, IMAGE_RECITATION) as finishReason: "content_filter" on chat streams, and as a content_filter error from structuredOutput and structuredOutputStream.

  • Updated dependencies [e8546f9, 5fd5355, 9393839, 215e339, 7157ef3]:

    • @tanstack/ai@1.3.0

@tanstack/ai-harness-cli@0.1.2

Patch Changes

@tanstack/ai-mcp@1.1.1

Patch Changes

@tanstack/ai-ollama@1.1.1

Patch Changes

  • #2077 c32f641 - Report finishReason: "length" on RUN_FINISHED when an Ollama stream ends with done_reason: "length". This includes a reply cut by num_predict, and a tool call cut the same way. A normal stop stays "stop". A finished tool call stays "tool_calls".

  • Updated dependencies [e8546f9, 5fd5355, 9393839, 215e339, 7157ef3]:

    • @tanstack/ai@1.3.0

@tanstack/ai-sandbox@1.2.1

Patch Changes

  • #2060 2753972 - Keep the harness tool calls of earlier runs in a saved thread. Before, withSandbox removed them from the chat transcript instead of only from the model request, so with withPersistence each run's save dropped the tool calls of the runs before it, and a reload showed those runs without their tool cards.

  • Updated dependencies [e8546f9, 5fd5355, 9393839, 215e339, 7157ef3]:

    • @tanstack/ai@1.3.0
    • @tanstack/ai-harness@0.3.0
    • @tanstack/ai-persistence@1.0.1
    • @tanstack/ai-skills@1.0.2

@tanstack/ai-skills@1.0.2

Patch Changes

@tanstack/openai-base@1.0.3

Patch Changes

  • #2087 5fd5355 - Keep Responses item ids and phases when adjacent answer text is merged. Save each item's text length so replay can restore its boundary.

  • Updated dependencies [e8546f9, 5fd5355, 9393839, 215e339, 7157ef3]:

    • @tanstack/ai@1.3.0

@coderabbitai

coderabbitai Bot commented Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

  • Source mode: Auto
  • Repository: TanStack/ai
  • Branch: main
  • File: .coderabbit.yaml
  • Commit: 9bcdd41
  • Layers: Repository YAML
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 5cebca35-fa8d-4a5d-b336-05b83bfe2757

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions
github-actions Bot force-pushed the changeset-release/main branch 5 times, most recently from 9b960f4 to 567c06d Compare November 9, 2026 03:25
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 567c06d to 4b118a3 Compare November 9, 2026 04:03
@AlemTuzlak
AlemTuzlak merged commit ea2b158 into main Nov 9, 2026
3 checks passed
@AlemTuzlak
AlemTuzlak deleted the changeset-release/main branch November 9, 2026 12:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant