Skip to content

Sync upstream 4.30 (next wave after the 4.29 cut) #135

Description

@patrick-chinchill

Status

0.4.29 cut in flight — PR #134 is the completion train for the 4.29 wave. This issue tracks the NEXT wave: upstream tagged chat@4.30.0 on 2026-06-01 (release commit a5b118f).

What's between chat@4.29.0 and chat@4.30.0

~21 commits touching packages/; 13 substantive after excluding docs/release bookkeeping (#575, #566, #568, #517, #562, #560, #557, a5b118f). Sizes are upstream packages/-only diffstats.

Slack low-level primitives wave (the headline — ~4,800 LOC across 6 commits)

A new public API layer of importable subpaths under chat/slack/*:

Python design question (resolve before porting): mirror as chat_sdk.slack_primitives / chat_sdk.adapters.slack.{webhook,format,api,blockkit} submodule re-exports? Much of the underlying logic already exists inside adapters/slack/ — this wave is largely re-exporting it as stable public API, so the port may be mostly module re-organization + tests, not new logic.

New adapter

Adapter features

Fixes

Carried over from 0.4.29

Acceptance criteria

  • UPSTREAM_PARITY = "4.30.0"
  • lint.yml re-pinned to chat@4.30.0; strict fidelity green at the new pin
  • All items above ported or documented as deferred in docs/UPSTREAM_SYNC.md
  • Version 0.4.30 cut with consolidated CHANGELOG

References

Activity

  1. coderabbitai commented on Jun 12, 2026

    @coderabbitai
    🔗 Related PRs

    #48 - fix: adapter hygiene — Slack stream await, Teams divider, public worker APIs [merged]
    #72 - ci(fidelity): ratchet-down baseline + wire into lint.yml [merged]
    #83 - sync: upstream v4.27.0 (alpha 1) [merged]
    #89 - fix(adapters): bug-fix sweep from upstream 4.27.0 (slack/discord/telegram) [merged]
    #106 - release: 0.4.27 — synced to upstream vercel/chat@4.27.0 [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. patrick-chinchill commented on Jun 21, 2026

    @patrick-chinchill
    CollaboratorAuthor

    Completed in 0.4.30 (released 2026-06-19) — new Twilio adapter, Teams adapter migration to the official SDK, Telegram native streaming, Slack primitives subpaths. See the 0.4.30 CHANGELOG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions