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
Upstream has moved on while the 4.27.0 sync (PRs #83, #85, #86, #87, #88, #89, #90) was in flight:
chat@4.28.0 — released between 4.27.0 (Apr 30) and 4.29.0 (May 18)
chat@4.29.0 — released 2026-05-18
When the 4.27 sync wave lands, we'll be ~3 weeks behind upstream. This issue tracks the next sync to catch up to 4.29.0.
Headline items from 4.28 + 4.29
Core (packages/chat)
New chat/ai subpath — createChatTools + toAiMessages for Vercel AI SDK integration. Substantial new public API surface; needs design discussion on the Python equivalent (do we plumb to Anthropic SDK / OpenAI SDK / something else?).
Burst concurrency strategy — new option beyond the existing drop / queue / debounce / concurrent. Likely a moderate port; depends on the upstream semantics.
Adapters
Adapter internals visibility: private → protected to enable subclassing. Python equivalent is a code-style audit — we use _underscore for protected; need to verify our subclass-ability matches upstream's new contract.
@chat-adapter/web: Vue + Svelte support. Out of scope for chat-sdk-python (no browser runtime).
@chat-adapter/tests (new package): testing utilities for adapter authors. Maybe useful to mirror as a Python helper module, maybe not — we have our own pattern.
Config
Configuration types reorganized for cross-package consistency, with backward-compatible deprecated aliases. Probably mechanical.
Teams adapter — migration window
Issue #93 (Teams adapter → microsoft-teams-apps Python SDK) is already tracked for 0.4.28. The natural cadence is:
0.4.27: ship the in-flight wave (hand-rolled streaming + bug fixes)
0.4.28 / 0.4.29: combined sync with the Teams SDK migration as the headline Teams change
This aligns nicely — the migration replaces our hand-rolled Bot Framework REST loop with the official SDK's ctx.stream.emit(), and lands inside the same release window as the upstream private → protected adapter visibility audit.
Background
Upstream has moved on while the 4.27.0 sync (PRs #83, #85, #86, #87, #88, #89, #90) was in flight:
When the 4.27 sync wave lands, we'll be ~3 weeks behind upstream. This issue tracks the next sync to catch up to 4.29.0.
Headline items from 4.28 + 4.29
Core (
packages/chat)chat/aisubpath —createChatTools+toAiMessagesfor Vercel AI SDK integration. Substantial new public API surface; needs design discussion on the Python equivalent (do we plumb to Anthropic SDK / OpenAI SDK / something else?).drop/queue/debounce/concurrent. Likely a moderate port; depends on the upstream semantics.Adapters
private→protectedto enable subclassing. Python equivalent is a code-style audit — we use_underscorefor protected; need to verify our subclass-ability matches upstream's new contract.@chat-adapter/telegram: improved attachment uploads + video note handling. Post-dates fix(telegram): MarkdownV2 rendering + telegram-chat reference example vercel/chat#407 (the MarkdownV2 fix already in fix(adapters): bug-fix sweep from upstream 4.27.0 (slack/discord/telegram) #89), so additive rather than conflicting.@chat-adapter/web: Vue + Svelte support. Out of scope for chat-sdk-python (no browser runtime).@chat-adapter/tests(new package): testing utilities for adapter authors. Maybe useful to mirror as a Python helper module, maybe not — we have our own pattern.Config
Teams adapter — migration window
Issue #93 (Teams adapter →
microsoft-teams-appsPython SDK) is already tracked for 0.4.28. The natural cadence is:This aligns nicely — the migration replaces our hand-rolled Bot Framework REST loop with the official SDK's
ctx.stream.emit(), and lands inside the same release window as the upstreamprivate→protectedadapter visibility audit.Suggested sync structure (mirroring 4.26 → 4.27 cadence)
chat/aisubpath port (likely the biggest individual PR)microsoft-teams-apps(issue Migrate Teams adapter to microsoft-teams-apps (official MS Python SDK) #93 — the headline Teams change)0.4.29, fidelity check, CHANGELOG roll-up)Out of scope
@chat-adapter/webVue/Svelte (no browser runtime in chat-sdk-python)@chat-adapter/testspackage (re-evaluate — may or may not port)Acceptance criteria
UPSTREAM_PARITY = "4.29.0"and version0.4.29chat@4.27.0tochat@4.29.0scripts/fidelity_baseline.jsonregenerated against 4.29.0UPSTREAM_SYNC.mdReferences
microsoft-teams-apps