chore(release): version packages

[github-actions]

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

@chat-adapter/whatsapp@4.37.0

Minor Changes

• 16879fd: Fix the WhatsAppInboundMessage.context type to model all documented webhook variants. The type previously declared context?: { from: string; id: string }, but Meta's Cloud API sends mutually exclusive context shapes: quoted replies carry from/id, forwarded messages carry only forwarded or frequently_forwarded (no id), and catalog product inquiries add referred_product. Code narrowed by the old type could dereference context.id and crash at runtime on forwarded messages. All context fields are now optional and the forwarded/product-inquiry fields are included. Consumers that dereference context.from or context.id without a guard will now see a type error, surfacing what was already a latent crash on forwarded messages.

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

chat@4.37.0

Minor Changes

• 85e3d22: Close residual gaps in agent read-tool scoping. createChatTools's read guard now wraps modal, assistant-thread, assistant-context, app-home, app-context, and member-joined dispatch so tools built in those handlers inherit the active conversation, and it logs a warning (instead of failing open silently) when a read runs with no resolvable scope. Scoping stays channel-level by default, so a thread scope still permits sibling threads in its channel. Pass the new strictScope: true to confine a thread scope to that thread alone, rejecting both sibling threads and the parent channel, which matters on platforms where a channel is the widest read available (a GitHub channel is an entire repo).

  Note that reads inside those newly wrapped handlers were previously unscoped. An agent built in an onModalSubmit, onAppHomeOpened, or onMemberJoinedChannel handler that reads another channel will now be rejected. Pass an explicit scope, or scope: false for intentionally workspace-wide reads.

@chat-adapter/discord@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/gchat@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/github@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/linear@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/messenger@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/shared@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0

@chat-adapter/slack@4.37.0

Patch Changes

• 6f0d2f0: Resolve outgoing @name mentions on the Slack native streaming path so streamed responses mention users consistently with the post-and-edit fallback. Committed renderer text is resolved incrementally, keeping fenced code literal and preserving the existing ambiguity semantics.
• c311827: Preserve the Slack channel ID when converting labeled channel tokens (<#C123|general> now becomes #general (C123)) so agents can pass the ID to channel tools, and normalize the commonly hallucinated <label|url> link order before Markdown conversion
• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/teams@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/telegram@4.37.0

Patch Changes

• 629e655: Combine incoming Telegram media groups into one message with ordered attachments and the shared caption.
• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/twilio@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/web@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/x@4.37.0

Patch Changes

• b674923: Restrict the X CRC challenge to the opaque token shape X sends before signing it. The endpoint previously returned an HMAC over any crc_token, which let a caller have an arbitrary webhook body signed and replay that as x-twitter-webhooks-signature on a forged POST. A webhook body is JSON and can no longer pass the token check, so a CRC response can't double as a POST event signature.
• Updated dependencies [85e3d22]
  • chat@4.37.0
  • @chat-adapter/shared@4.37.0

@chat-adapter/state-ioredis@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0

@chat-adapter/state-memory@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0

@chat-adapter/state-pg@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0

@chat-adapter/state-redis@4.37.0

Patch Changes

• Updated dependencies [85e3d22]
  • chat@4.37.0

@chat-adapter/tests@4.37.0

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
chat	Ready	Preview, v0	Aug 3, 2026 2:01pm
chat-sdk-nextjs-chat	Ready	Preview	Aug 3, 2026 2:01pm