Skip to content

sync: upstream v4.27.0 (alpha 1) #83

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
patrick-chinchill wants to merge 4 commits into
base: main
Choose a base branch
from
Draft

sync: upstream v4.27.0 (alpha 1) #83

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
adc1440
sync: upstream v4.27.0 (alpha 1)
claude May 7, 2026
f88a272
docs(changelog): qualify upstream PR refs with vercel/chat# prefix
claude May 7, 2026
530c42d
docs(sync): tick CHANGELOG checkboxes + document Teams SDK 2.0.8 N/A
claude May 10, 2026
d6b267f
test(chat): align concurrency test names with upstream chat.test.ts
claude May 10, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
71 changes: 71 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,76 @@
# Changelog

## 0.4.27a1 (2026-05-07)

Alpha sync starter for upstream `4.27.0` (`vercel/chat` release commit
`f55378a`, Apr 30 2026). **No feature ports in this release** — this is a
parity-bookkeeping bump that establishes the sync branch, sets
`UPSTREAM_PARITY = "4.27.0"`, and lays out the porting plan below. Each
substantive commit lands as its own PR (matching the cadence used during
the `4.26.0` sync: #64, #66, #67, #74, etc.).

### Upstream tagging note

Upstream cut versions for the entire monorepo on Apr 30 2026 (commit
`f55378a`), bumping `packages/chat/package.json` from `4.26.0` to
`4.27.0`. As of this writing only `@chat-adapter/shared@4.27.0` got a
git tag — no `chat@4.27.0` tag was published. The fidelity workflow
(`scripts/verify_test_fidelity.py`, `.github/workflows/lint.yml`)
therefore stays pinned to `chat@4.26.0` until either the tag is
published upstream or the first feature port lands and we move the pin
to commit `f55378a` directly. Local devs running fidelity in baseline
mode will see a `chat@4.26.0` vs `chat@4.27.0` mismatch — that's the
intended in-flight signal.

### Sync scope (22 substantive upstream commits between `chat@4.26.0..f55378a`)

#### Core (`packages/chat/` → `src/chat_sdk/`)

- [ ] **`chat.getUser(adapter, userId)`** for cross-platform user lookups (#391, upstream commit `a520797`). Adapter-side: each adapter exposes `getUser`. Touches `chat.py`, `types.py` (`User` type extension), and every adapter (`slack`, `teams`, `gchat`, `telegram`, `discord`, `whatsapp`, `github`, `linear`).
- [ ] **`ExternalSelect.initial_option` + `option_groups`** (#410, `70281dc`). Type extension in `types.py`; Slack adapter must serialize `option_groups` to Block Kit.
- [ ] **`thread.post()` streaming options** (#388, `9093292`). New params plumb through `Thread.post` → `chat.py` orchestrator.
- [ ] **Slack streaming team ID fix for interactive payloads** (#330, `8a0c7b3`). Bug fix in the Slack streaming path; check `adapters/slack/adapter.py` request-context plumbing.
- [ ] **Bundled guide markdown + templates manifest** (#423, `b0ab804`). Decision: skip or copy `packages/chat/resources/guides/*.md` and `templates.json` verbatim. Probably skip — these are TS-monorepo authoring resources, not runtime behavior.
- [x] **`concurrency.maxConcurrent` honored in `concurrent` strategy** (#419, `d630e6c`). Already addressed in the Python port — see the existing `ConcurrencyConfig.max_concurrent` row in `docs/UPSTREAM_SYNC.md` (we enforce via `asyncio.Semaphore` and reject misconfiguration). Upstream has now caught up; on this sync the divergence row downgrades from "silent correctness bug upstream" to "behavior parity restored".

#### Slack (`packages/adapter-slack/` → `src/chat_sdk/adapters/slack/`)

- [ ] **Slack Socket Mode support** (#162, `7e9d0fc`). Big — adds a persistent WebSocket transport alongside HTTP webhooks. Decision: in scope or follow-up? Mirrors the Discord Gateway gap already documented in non-parity ("HTTP interactions only").
- [ ] **Dynamic `bot_token` resolver + custom `webhookVerifier`** (#421, `2531e9c`). Multi-workspace pattern; touches `SlackAdapter.__init__` and request handling.
- [ ] **External-select Block Kit support** (#397, `a179b29`). Pairs with the core `option_groups` change above.
- [ ] **Native `markdown_text` for outgoing messages** (#440, post-release — Apr 17). NOTE: this commit is post-`f55378a` so technically out of `4.27.0` scope, but listed here because the team often picks up post-release fixes.
- [ ] **Link-preview unfurl metadata enrichment** (#395, `ded6f78`).
- [ ] **`@mention` regex preserves email addresses** (#394, `c26ee6c`).
- [ ] **Guard against empty `threadTs` (`invalid_thread_ts` fix)** (#292, `53c6b68`).

#### Teams (`packages/adapter-teams/` → `src/chat_sdk/adapters/teams/`)

- [ ] **Native streaming for DMs via `emit`** (#416, `ed46bae`). Currently the Python port falls back to `_fallback_stream` for Teams; native streaming would lift that.
- [ ] **DM conversation ID resolution for Graph API** (#403, `4c24c94`). Bug fix.
- [ ] **Teams SDK 2.0.8 + `User-Agent` header** (#415, `885a471`). TS-side dependency bump; Python equivalent is to verify our `botbuilder` pin and propagate `User-Agent` if not already.

#### Telegram

- [ ] **MarkdownV2 rendering fixes** (#407, `b9a1961`). Pairs with the streaming-chunk safety trim in #446 (post-`f55378a`).

#### Discord

- [ ] **Don't duplicate text when posting card messages** (#256, `7e5b447`). Confirm Python port's `discord/cards.py` doesn't have the same bug.
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot May 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The pull request references in the sync scope section (e.g., #391, #410, #388) refer to upstream vercel/chat PRs. Without the repository prefix, GitHub will attempt to link these to pull requests within this repository, which is confusing given that local PR numbers (like #64 in line 10) are also mentioned. Please use the full reference format (e.g., vercel/chat#391) to ensure they link correctly to the upstream source.

Copy link
Copy Markdown
Collaborator Author

@patrick-chinchill patrick-chinchill May 15, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Addressed in commit f88a272 (docs(changelog): qualify upstream PR refs with vercel/chat# prefix), which landed shortly after this review and qualified all 14 upstream PR refs in CHANGELOG.md with the vercel/chat# prefix. The thread is now is_outdated: true against the current CHANGELOG.md (head d6b267f); local PR refs (#64, #74, #82, plus the in-flight #84–#90) remain bare so GitHub still cross-links them within this repo. Marking as resolved.

Generated by Claude Code


#### Out of scope for this Python port

- **`@chat-adapter/web`** — new package adding a browser chat UI for chat-sdk bots (#444). No browser runtime in chat-sdk-python.
- **Documentation site changes** — `apps/docs/`, README/changelog tweaks, dependency bumps.

### Workflow

1. This alpha PR establishes the sync. CI on this draft is intentionally not invoked (lint.yml is gated on `!github.event.pull_request.draft`).
2. Each item above lands as its own PR, following the same pattern as the `4.26.0` cycle. Each port PR:
- Updates the relevant `MAPPING` / fidelity coverage and removes its entries from `scripts/fidelity_baseline.json` if previously baselined.
- Bumps lint.yml's pinned upstream ref to commit `f55378a` (or a later SHA if upstream cuts a `chat@4.27.0` tag in the meantime).
- Adds an entry under the next `CHANGELOG` heading (`0.4.27a2`, `0.4.27a3`, …).
3. Once all 22 items are ported (or explicitly documented as divergence in `docs/UPSTREAM_SYNC.md`), the final PR cuts `0.4.27` and switches CI back to strict fidelity at the upstream tag.

## 0.4.26.3 (2026-05-07)

Python-only fix. No upstream version change.
Expand Down
17 changes: 11 additions & 6 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Claude Code Quick Reference -- chat-sdk-python

## What is this?
Python port of [Vercel Chat SDK](https://github.com/vercel/chat) (v4.26.0). Multi-platform async chat framework.
Python port of [Vercel Chat SDK](https://github.com/vercel/chat) (porting v4.27.0; last fully-synced release `0.4.26.3` at upstream `4.26.0`). Multi-platform async chat framework.

## Key Commands
```bash
Expand All @@ -23,7 +23,8 @@ Our version embeds the upstream Vercel Chat version: `0.{upstream_major}.{upstre
- `0.4.25` = synced to upstream `4.25.0`
- `0.4.25.1` = Python-only fix on top of `4.25.0`
- `0.4.26` = synced to upstream `4.26.0`
- `0.4.26a1` = alpha while porting upstream `4.26.0`
- `0.4.26.3` = last fully-synced release (Python-only fixes on top of `4.26.0`)
- `0.4.27a1` = alpha while porting upstream `4.27.0` (current branch)
- `UPSTREAM_PARITY` constant in `__init__.py` = programmatic access

## Architecture
Expand Down Expand Up @@ -106,16 +107,20 @@ will not pass CI.

**Fidelity check** (`scripts/verify_test_fidelity.py`) verifies every TS
`it("...")` in the mapped core files has a matching Python `def test_*()`,
pinned to `chat@4.26.0`. The `MAPPING` dict in that script is the
authoritative scope list — it currently covers 8 of 17
`packages/chat/src/*.test.ts` files (extending it is tracked as a
pinned to `chat@4.26.0` (the last fully-synced upstream tag — `chat@4.27.0`
is in flight; pin moves as ports land in this sync cycle). The `MAPPING`
dict in that script is the authoritative scope list — it currently covers 8
of 17 `packages/chat/src/*.test.ts` files (extending it is tracked as a
follow-up). **CI runs `--strict`** (see `.github/workflows/lint.yml`):
any missing translation in a mapped file fails the build, and a missing
upstream checkout also fails (the script exits non-zero when any mapped
TS file isn't found). Baseline mode (the default without `--strict`) is
retained for local workflows where a few ports land in flight —
regenerate via `--update-baseline` after documenting intentional
divergence in `docs/UPSTREAM_SYNC.md`.
divergence in `docs/UPSTREAM_SYNC.md`. During this sync cycle baseline
mode reports a parity mismatch (baseline pinned at `chat@4.26.0`,
`UPSTREAM_PARITY` says `4.27.0`); that's the intended signal until the
sync lands.

Before the fidelity check can run locally, clone the pinned upstream
checkout (same command CI uses in `lint.yml`):
Expand Down
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@

Multi-platform async chat SDK for Python. Port of [Vercel Chat](https://github.com/vercel/chat).

> **Status: Alpha (0.4.26 — synced to [Vercel Chat 4.26.0](https://github.com/vercel/chat))** — API may change.
> **Status: Alpha (0.4.27a1 — porting [Vercel Chat 4.27.0](https://github.com/vercel/chat))** — API may change. Last fully-synced release: `0.4.26.3` (parity with upstream `chat@4.26.0`). See [CHANGELOG.md](CHANGELOG.md) for the in-flight sync plan.

## Why chat-sdk?

Expand Down
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[project]
name = "chat-sdk"
version = "0.4.26.3"
version = "0.4.27a1"
description = "Multi-platform async chat SDK for Python — port of Vercel Chat"
keywords = [
"chat",
Expand Down
2 changes: 1 addition & 1 deletion src/chat_sdk/__init__.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,7 +185,7 @@
)

# The upstream Vercel Chat version this release is synced to.
UPSTREAM_PARITY = "4.26.0"
UPSTREAM_PARITY = "4.27.0"

__all__ = [
"UPSTREAM_PARITY",
Expand Down
Loading