ci: Version Packages#968
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 21, 2026 09:07
675d369 to
627dc65
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 21, 2026 13:05
627dc65 to
043cde6
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
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@0.43.0
Minor Changes
#955
7c7aa09- Resumable streams: reconnect to an in-flight SSE or NDJSON response withoutre-running the provider.
toServerSentEventsResponseandtoHttpResponseboth accept adurability: { adapter, batch }option. The adapter (StreamDurability)records every chunk to an ordered log before delivery and tags each event with
an opaque, adapter-owned offset — an SSE
id:line, or theidof an NDJSON{ id, chunk }envelope (NDJSON has no native event-id). A reconnect(
Last-Event-ID) or an explicit?offsetread replays strictly after thatoffset from the log — the lazy provider stream is never iterated on resume.
Producers terminalize the log on cancellation and failure (
RUN_ERRORappendclose()) and on completion when the source stream emits its own terminalevent (
chat()always does), so readers are never parked on a dead run.Two adapters ship:
memoryStream(request)in@tanstack/ai(process-local,for development and tests) and the new
@tanstack/ai-durable-streampackage,a Durable Streams protocol adapter for production backends.
For the
GEThandler that a reload or a second tab reconnects to,resumeServerSentEventsResponse({ adapter })andresumeHttpResponse({ adapter })replay a run straight from the durability log. They need no producer stream and
return a 400 when the request carries no resume offset.
On the client, all four HTTP adapters are now resumable —
fetchServerSentEvents,fetchHttpStream,xhrServerSentEvents, andxhrHttpStream. Each tracks theper-event offset, auto-reconnects with
Last-Event-ID, de-duplicates thereplayed prefix, and exposes
joinRun(runId)to attach to an in-flight orfinished run from the start (read-only GET with
offset=-1). Untagged streamsbehave exactly as before. A durable run that ends with no terminal event and no
forward progress now throws
DurableStreamIncompleteErrorinstead of hanging.Reconnection and durability are bounded so failures surface rather than hang or
loop:
memoryStreamevicts completed logs after a grace window (unbounded growthis gone); resuming an expired/unknown run throws, and a from-start join to a
run that never produces fails after
MemoryStreamOptions.firstChunkDeadlineMs.reconnect: { maxAttempts, delayMs }— athrottle plus a ceiling on CONSECUTIVE no-progress reconnects (default 5;
forward progress resets it) that fails with the new
StreamReconnectLimitErrorinstead of reconnecting endlessly, without penalizing a healthy long-lived run.
durableStreamacceptsreconnect: { maxReadFailures, delayMs }to bound itsread-retry loop, and
serveris now optional whenfetchis provided (e.g. aCloudflare service binding).
toServerSentEventsResponseacceptsdebugto record durability terminal /close failures server-side, where a replaying joiner cannot observe them.
@tanstack/ai-client@0.23.0
Minor Changes
#955
7c7aa09- Resumable streams: reconnect to an in-flight SSE or NDJSON response withoutre-running the provider.
toServerSentEventsResponseandtoHttpResponseboth accept adurability: { adapter, batch }option. The adapter (StreamDurability)records every chunk to an ordered log before delivery and tags each event with
an opaque, adapter-owned offset — an SSE
id:line, or theidof an NDJSON{ id, chunk }envelope (NDJSON has no native event-id). A reconnect(
Last-Event-ID) or an explicit?offsetread replays strictly after thatoffset from the log — the lazy provider stream is never iterated on resume.
Producers terminalize the log on cancellation and failure (
RUN_ERRORappendclose()) and on completion when the source stream emits its own terminalevent (
chat()always does), so readers are never parked on a dead run.Two adapters ship:
memoryStream(request)in@tanstack/ai(process-local,for development and tests) and the new
@tanstack/ai-durable-streampackage,a Durable Streams protocol adapter for production backends.
For the
GEThandler that a reload or a second tab reconnects to,resumeServerSentEventsResponse({ adapter })andresumeHttpResponse({ adapter })replay a run straight from the durability log. They need no producer stream and
return a 400 when the request carries no resume offset.
On the client, all four HTTP adapters are now resumable —
fetchServerSentEvents,fetchHttpStream,xhrServerSentEvents, andxhrHttpStream. Each tracks theper-event offset, auto-reconnects with
Last-Event-ID, de-duplicates thereplayed prefix, and exposes
joinRun(runId)to attach to an in-flight orfinished run from the start (read-only GET with
offset=-1). Untagged streamsbehave exactly as before. A durable run that ends with no terminal event and no
forward progress now throws
DurableStreamIncompleteErrorinstead of hanging.Reconnection and durability are bounded so failures surface rather than hang or
loop:
memoryStreamevicts completed logs after a grace window (unbounded growthis gone); resuming an expired/unknown run throws, and a from-start join to a
run that never produces fails after
MemoryStreamOptions.firstChunkDeadlineMs.reconnect: { maxAttempts, delayMs }— athrottle plus a ceiling on CONSECUTIVE no-progress reconnects (default 5;
forward progress resets it) that fails with the new
StreamReconnectLimitErrorinstead of reconnecting endlessly, without penalizing a healthy long-lived run.
durableStreamacceptsreconnect: { maxReadFailures, delayMs }to bound itsread-retry loop, and
serveris now optional whenfetchis provided (e.g. aCloudflare service binding).
toServerSentEventsResponseacceptsdebugto record durability terminal /close failures server-side, where a replaying joiner cannot observe them.
Patch Changes
7c7aa09]:@tanstack/ai-durable-stream@0.1.0
Minor Changes
#955
7c7aa09- Resumable streams: reconnect to an in-flight SSE or NDJSON response withoutre-running the provider.
toServerSentEventsResponseandtoHttpResponseboth accept adurability: { adapter, batch }option. The adapter (StreamDurability)records every chunk to an ordered log before delivery and tags each event with
an opaque, adapter-owned offset — an SSE
id:line, or theidof an NDJSON{ id, chunk }envelope (NDJSON has no native event-id). A reconnect(
Last-Event-ID) or an explicit?offsetread replays strictly after thatoffset from the log — the lazy provider stream is never iterated on resume.
Producers terminalize the log on cancellation and failure (
RUN_ERRORappendclose()) and on completion when the source stream emits its own terminalevent (
chat()always does), so readers are never parked on a dead run.Two adapters ship:
memoryStream(request)in@tanstack/ai(process-local,for development and tests) and the new
@tanstack/ai-durable-streampackage,a Durable Streams protocol adapter for production backends.
For the
GEThandler that a reload or a second tab reconnects to,resumeServerSentEventsResponse({ adapter })andresumeHttpResponse({ adapter })replay a run straight from the durability log. They need no producer stream and
return a 400 when the request carries no resume offset.
On the client, all four HTTP adapters are now resumable —
fetchServerSentEvents,fetchHttpStream,xhrServerSentEvents, andxhrHttpStream. Each tracks theper-event offset, auto-reconnects with
Last-Event-ID, de-duplicates thereplayed prefix, and exposes
joinRun(runId)to attach to an in-flight orfinished run from the start (read-only GET with
offset=-1). Untagged streamsbehave exactly as before. A durable run that ends with no terminal event and no
forward progress now throws
DurableStreamIncompleteErrorinstead of hanging.Reconnection and durability are bounded so failures surface rather than hang or
loop:
memoryStreamevicts completed logs after a grace window (unbounded growthis gone); resuming an expired/unknown run throws, and a from-start join to a
run that never produces fails after
MemoryStreamOptions.firstChunkDeadlineMs.reconnect: { maxAttempts, delayMs }— athrottle plus a ceiling on CONSECUTIVE no-progress reconnects (default 5;
forward progress resets it) that fails with the new
StreamReconnectLimitErrorinstead of reconnecting endlessly, without penalizing a healthy long-lived run.
durableStreamacceptsreconnect: { maxReadFailures, delayMs }to bound itsread-retry loop, and
serveris now optional whenfetchis provided (e.g. aCloudflare service binding).
toServerSentEventsResponseacceptsdebugto record durability terminal /close failures server-side, where a replaying joiner cannot observe them.
Patch Changes
7c7aa09]:@tanstack/ai-acp@0.2.4
Patch Changes
7c7aa09]:@tanstack/ai-angular@0.3.2
Patch Changes
7c7aa09]:@tanstack/ai-anthropic@0.16.4
Patch Changes
7c7aa09]:@tanstack/ai-bedrock@0.1.5
Patch Changes
7c7aa09]:@tanstack/ai-claude-code@0.2.4
Patch Changes
7c7aa09]:@tanstack/ai-code-mode@0.3.9
Patch Changes
7c7aa09]:@tanstack/ai-code-mode-skills@0.3.12
Patch Changes
7c7aa09]:@tanstack/ai-codex@0.2.4
Patch Changes
7c7aa09]:@tanstack/ai-devtools-core@0.4.25
Patch Changes
7c7aa09]:@tanstack/ai-elevenlabs@0.2.35
Patch Changes
7c7aa09]:@tanstack/ai-fal@0.9.13
Patch Changes
7c7aa09]:@tanstack/ai-gemini@0.20.2
Patch Changes
7c7aa09]:@tanstack/ai-grok@0.14.10
Patch Changes
7c7aa09]:@tanstack/ai-grok-build@0.2.4
Patch Changes
7c7aa09]:@tanstack/ai-groq@0.5.4
Patch Changes
7c7aa09]:@tanstack/ai-isolate-cloudflare@0.2.39
Patch Changes
@tanstack/ai-isolate-node@0.1.48
Patch Changes
@tanstack/ai-isolate-quickjs@0.1.48
Patch Changes
@tanstack/ai-mcp@0.2.6
Patch Changes
7c7aa09]:@tanstack/ai-mistral@0.2.4
Patch Changes
7c7aa09]:@tanstack/ai-ollama@0.8.17
Patch Changes
7c7aa09]:@tanstack/ai-openai@0.17.2
Patch Changes
7c7aa09]:@tanstack/ai-opencode@0.2.4
Patch Changes
7c7aa09]:@tanstack/ai-openrouter@0.15.11
Patch Changes
7c7aa09]:@tanstack/ai-preact@0.11.2
Patch Changes
7c7aa09]:@tanstack/ai-react@0.18.2
Patch Changes
7c7aa09]:@tanstack/ai-react-ui@0.8.16
Patch Changes
7c7aa09]:@tanstack/ai-sandbox@0.2.5
Patch Changes
7c7aa09]:@tanstack/ai-sandbox-cloudflare@0.2.5
Patch Changes
7c7aa09]:@tanstack/ai-solid@0.15.2
Patch Changes
7c7aa09]:@tanstack/ai-solid-ui@0.7.15
Patch Changes
7c7aa09]:@tanstack/ai-svelte@0.15.2
Patch Changes
7c7aa09]:@tanstack/ai-vue@0.15.2
Patch Changes
7c7aa09]:@tanstack/ai-vue-ui@0.2.35
Patch Changes
@tanstack/openai-base@0.9.10
Patch Changes
7c7aa09]:@tanstack/preact-ai-devtools@0.1.68
Patch Changes
@tanstack/react-ai-devtools@0.2.68
Patch Changes
@tanstack/solid-ai-devtools@0.2.68
Patch Changes
ag-ui@0.0.3
Patch Changes
7c7aa09]: