Skip to content

Sync upstream 4.28 + 4.29 (next sync after 4.27 wave lands) #98

@patrick-chinchill

Description

@patrick-chinchill

Status (updated 2026-05-28)

0.4.27 shipped (release c43ea05 on main, tag v0.4.27). Wave 4.27 → 4.29 now in flight.

Background

Upstream has moved on while the 4.27 sync (PRs #83, #85, #86, #87, #88, #89, #90) was in flight:

  • chat@4.27.0 — NEVER got a chat@* tag (only @chat-adapter/shared@4.27.0)
  • chat@4.28.0 — NEVER got a chat@* tag
  • chat@4.29.0 — released 2026-05-18, now tagged

chat@4.29.0 is the next real upstream tag and the target for this sync.

What's between our 0.4.27 baseline and chat@4.29.0

37 substantive commits in packages/. Already-covered items (no work):

Sync scope (TODO)

Core (packages/chat)

All adapters

Slack

Discord

Telegram

Teams

New packages

Open questions

  1. Cadence: one wave (4.27 → 4.29) or split (4.27 → 4.28, then 4.28 → 4.29)? Default in PR sync: upstream v4.29.0 (alpha 1) #108: one wave.
  2. Python floor bump to 3.12 (required for Teams SDK migration). Confirm chinchill-api compatibility.
  3. Discord Gateway scope: ship Gateway support in this wave (issue Discord adapter: port native Gateway WebSocket support (HTTP-only today) #57) or keep #490 isolated?
  4. adapter.client rename: deprecation shim for one release, or hard cutover?
  5. Plus the chat/ai-specific and Messenger-specific questions in Design: chat/ai subpath port (vercel/chat#492) #109 and Design: Messenger (Meta) adapter port (vercel/chat#461) #110.

Acceptance criteria (carried from original filing)

References

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions