Skip to content

chore(release): version packages - #841

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore(release): version packages#841
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

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/shared@4.39.0

Minor Changes

  • 153bd96: guard Messenger attachment downloads against SSRF and oversized responses

    downloadAttachment in @chat-adapter/shared accepts an optional hosts allowlist that restricts downloads, including redirect targets, to the given hosts and their subdomains. The Messenger adapter uses it to download attachment media only from Meta's fbsbx.com and fbcdn.net hosts, with the shared SSRF guard, 25 MB size cap, and 30 second timeout. External fallback and link-share URLs are rejected before any network request.

  • bb92688: secure anonymous attachment downloads against SSRF and oversized responses

    @chat-adapter/shared gains downloadAttachment, a guarded downloader that refuses private and internal addresses (as URL literals, through DNS resolution, and after redirects), decodes compressed responses, caps the body size at 25 MB, and bounds the whole download with a 30 second timeout. All of these are configurable, including the transport for proxied deployments.

    The Teams adapter uses it for anonymous attachment downloads. HTTPS attachments on any public host keep working, plain-HTTP URLs are refused, and the Bot Framework Emulator's loopback connector now uses bot authentication so local development keeps working.

  • b6fa24c: guard attachment downloads across the remaining adapters

    Slack, Discord, and WhatsApp attachment downloads now go through the shared guarded downloader: private and internal addresses are refused (as URL literals, through DNS resolution, and after redirects), responses are capped at 25 MB, and downloads time out after 30 seconds. Slack sends the bot token only on hops to trusted Slack origins, and WhatsApp keeps its access token on Meta's media hosts and the configured Graph origin. Telegram enforces the same size cap and timeout with the Web Fetch API so downloads keep working in runtimes like Cloudflare Workers.

    downloadAttachment in @chat-adapter/shared now resolves headers per hop (pass a function to control what each redirect target receives), forwards the resolved headers to custom transports, and accepts an onResponse hook to reject unexpected final responses before the body is read.

Patch Changes

@chat-adapter/slack@4.39.0

Minor Changes

  • 2ce2be0: Add Slack Agent Sessions lifecycle support, native stop cancellation through thread.signal, automatic session titles, and session stop/title-change events while preserving the legacy assistant_view compatibility path.

Patch Changes

  • 7c26965: prevent attachment downloads from sending credentials to untrusted hosts

  • b6fa24c: guard attachment downloads across the remaining adapters

    Slack, Discord, and WhatsApp attachment downloads now go through the shared guarded downloader: private and internal addresses are refused (as URL literals, through DNS resolution, and after redirects), responses are capped at 25 MB, and downloads time out after 30 seconds. Slack sends the bot token only on hops to trusted Slack origins, and WhatsApp keeps its access token on Meta's media hosts and the configured Graph origin. Telegram enforces the same size cap and timeout with the Web Fetch API so downloads keep working in runtimes like Cloudflare Workers.

    downloadAttachment in @chat-adapter/shared now resolves headers per hop (pass a function to control what each redirect target receives), forwards the resolved headers to custom transports, and accepts an onResponse hook to reject unexpected final responses before the body is read.

  • Updated dependencies [2ce2be0]

  • Updated dependencies [153bd96]

  • Updated dependencies [16ea171]

  • Updated dependencies [eddcd7e]

  • Updated dependencies [bb92688]

  • Updated dependencies [929878b]

  • Updated dependencies [500b7e6]

  • Updated dependencies [b6fa24c]

    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/telegram@4.39.0

Minor Changes

  • c4a359e: require webhook verification by default with an explicit unverified opt-in
  • d5ebec1: Implement reply in the Telegram adapter so Thread.reply() threads the answer to its target instead of throwing NotImplementedError. The reference travels as Bot API reply_parameters and covers text, rich messages, documents, attachments and media groups; allow_sending_without_reply keeps delivery working when the target has been deleted. Malformed reply target ids are rejected before anything is sent, and a rich-message gateway that rejects reply_parameters falls back to a regular threaded send.

Patch Changes

  • eddcd7e: Return Telegram file downloads as portable ArrayBuffer data while preserving Buffer support in the shared attachment contract.

  • b6fa24c: guard attachment downloads across the remaining adapters

    Slack, Discord, and WhatsApp attachment downloads now go through the shared guarded downloader: private and internal addresses are refused (as URL literals, through DNS resolution, and after redirects), responses are capped at 25 MB, and downloads time out after 30 seconds. Slack sends the bot token only on hops to trusted Slack origins, and WhatsApp keeps its access token on Meta's media hosts and the configured Graph origin. Telegram enforces the same size cap and timeout with the Web Fetch API so downloads keep working in runtimes like Cloudflare Workers.

    downloadAttachment in @chat-adapter/shared now resolves headers per hop (pass a function to control what each redirect target receives), forwards the resolved headers to custom transports, and accepts an onResponse hook to reject unexpected final responses before the body is read.

  • Updated dependencies [2ce2be0]

  • Updated dependencies [153bd96]

  • Updated dependencies [16ea171]

  • Updated dependencies [eddcd7e]

  • Updated dependencies [bb92688]

  • Updated dependencies [929878b]

  • Updated dependencies [500b7e6]

  • Updated dependencies [b6fa24c]

    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

chat@4.39.0

Minor Changes

  • 2ce2be0: Add Slack Agent Sessions lifecycle support, native stop cancellation through thread.signal, automatic session titles, and session stop/title-change events while preserving the legacy assistant_view compatibility path.

Patch Changes

  • 16ea171: preserve adapter-returned thread ids when editing channel messages

  • eddcd7e: Return Telegram file downloads as portable ArrayBuffer data while preserving Buffer support in the shared attachment contract.

  • 929878b: Allow JSX link buttons to include an explicit action ID.

  • 500b7e6: enforce the conversation scope on write tools and stop trusting client-supplied message history in the web adapter

    createChatTools now runs the same scope guard on write tools that read tools already used, so a thread or channel id the model supplies that resolves outside the scoped conversation is rejected before the write executes. sendDirectMessage targets a user id rather than a conversation and stays gated by approval alone.

    The web adapter no longer treats the request body's messages array as a source of conversation state. Only the latest user message is consumed, and tool parts are stripped from it so a browser cannot inject forged tool-call or approval state. Text, file, and custom data parts pass through unchanged; a message left with no parts after stripping is rejected with HTTP 400. Prior turns come from the state adapter when persistMessageHistory is enabled.

@chat-adapter/discord@4.39.0

Patch Changes

  • c4f709f: fix edits, deletes, and reactions on Discord thread starter messages

    Operations on a thread's starter message now try the thread first and fall back to the parent channel when Discord reports the message as unknown. Threads on a text channel keep their starter message in the parent channel, so those operations used to fail; forum and media posts keep theirs in the thread and are unaffected.

    Note that deleting a text-channel thread's starter message now deletes the message, which Discord cascades into deleting the thread.

  • b6fa24c: guard attachment downloads across the remaining adapters

    Slack, Discord, and WhatsApp attachment downloads now go through the shared guarded downloader: private and internal addresses are refused (as URL literals, through DNS resolution, and after redirects), responses are capped at 25 MB, and downloads time out after 30 seconds. Slack sends the bot token only on hops to trusted Slack origins, and WhatsApp keeps its access token on Meta's media hosts and the configured Graph origin. Telegram enforces the same size cap and timeout with the Web Fetch API so downloads keep working in runtimes like Cloudflare Workers.

    downloadAttachment in @chat-adapter/shared now resolves headers per hop (pass a function to control what each redirect target receives), forwards the resolved headers to custom transports, and accepts an onResponse hook to reject unexpected final responses before the body is read.

  • Updated dependencies [2ce2be0]

  • Updated dependencies [153bd96]

  • Updated dependencies [16ea171]

  • Updated dependencies [eddcd7e]

  • Updated dependencies [bb92688]

  • Updated dependencies [929878b]

  • Updated dependencies [500b7e6]

  • Updated dependencies [b6fa24c]

    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/gchat@4.39.0

Patch Changes

  • Updated dependencies [2ce2be0]
  • Updated dependencies [153bd96]
  • Updated dependencies [16ea171]
  • Updated dependencies [eddcd7e]
  • Updated dependencies [bb92688]
  • Updated dependencies [929878b]
  • Updated dependencies [500b7e6]
  • Updated dependencies [b6fa24c]
    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/github@4.39.0

Patch Changes

  • Updated dependencies [2ce2be0]
  • Updated dependencies [153bd96]
  • Updated dependencies [16ea171]
  • Updated dependencies [eddcd7e]
  • Updated dependencies [bb92688]
  • Updated dependencies [929878b]
  • Updated dependencies [500b7e6]
  • Updated dependencies [b6fa24c]
    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/instagram@4.39.0

Patch Changes

  • Updated dependencies [2ce2be0]
  • Updated dependencies [153bd96]
  • Updated dependencies [16ea171]
  • Updated dependencies [eddcd7e]
  • Updated dependencies [bb92688]
  • Updated dependencies [929878b]
  • Updated dependencies [500b7e6]
  • Updated dependencies [b6fa24c]
    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/linear@4.39.0

Patch Changes

  • Updated dependencies [2ce2be0]
  • Updated dependencies [153bd96]
  • Updated dependencies [16ea171]
  • Updated dependencies [eddcd7e]
  • Updated dependencies [bb92688]
  • Updated dependencies [929878b]
  • Updated dependencies [500b7e6]
  • Updated dependencies [b6fa24c]
    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/messenger@4.39.0

Patch Changes

  • 153bd96: guard Messenger attachment downloads against SSRF and oversized responses

    downloadAttachment in @chat-adapter/shared accepts an optional hosts allowlist that restricts downloads, including redirect targets, to the given hosts and their subdomains. The Messenger adapter uses it to download attachment media only from Meta's fbsbx.com and fbcdn.net hosts, with the shared SSRF guard, 25 MB size cap, and 30 second timeout. External fallback and link-share URLs are rejected before any network request.

  • Updated dependencies [2ce2be0]

  • Updated dependencies [153bd96]

  • Updated dependencies [16ea171]

  • Updated dependencies [eddcd7e]

  • Updated dependencies [bb92688]

  • Updated dependencies [929878b]

  • Updated dependencies [500b7e6]

  • Updated dependencies [b6fa24c]

    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/notion@4.39.0

Patch Changes

  • Updated dependencies [2ce2be0]
  • Updated dependencies [153bd96]
  • Updated dependencies [16ea171]
  • Updated dependencies [eddcd7e]
  • Updated dependencies [bb92688]
  • Updated dependencies [929878b]
  • Updated dependencies [500b7e6]
  • Updated dependencies [b6fa24c]
    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/teams@4.39.0

Patch Changes

  • 63997ac: hydrate live Teams sender email without requiring Microsoft Graph permissions

  • bb92688: secure anonymous attachment downloads against SSRF and oversized responses

    @chat-adapter/shared gains downloadAttachment, a guarded downloader that refuses private and internal addresses (as URL literals, through DNS resolution, and after redirects), decodes compressed responses, caps the body size at 25 MB, and bounds the whole download with a 30 second timeout. All of these are configurable, including the transport for proxied deployments.

    The Teams adapter uses it for anonymous attachment downloads. HTTPS attachments on any public host keep working, plain-HTTP URLs are refused, and the Bot Framework Emulator's loopback connector now uses bot authentication so local development keeps working.

  • Updated dependencies [2ce2be0]

  • Updated dependencies [153bd96]

  • Updated dependencies [16ea171]

  • Updated dependencies [eddcd7e]

  • Updated dependencies [bb92688]

  • Updated dependencies [929878b]

  • Updated dependencies [500b7e6]

  • Updated dependencies [b6fa24c]

    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/twilio@4.39.0

Patch Changes

  • 28bc776: isolate Twilio message processing locks by conversation
  • Updated dependencies [2ce2be0]
  • Updated dependencies [153bd96]
  • Updated dependencies [16ea171]
  • Updated dependencies [eddcd7e]
  • Updated dependencies [bb92688]
  • Updated dependencies [929878b]
  • Updated dependencies [500b7e6]
  • Updated dependencies [b6fa24c]
    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/web@4.39.0

Patch Changes

  • 500b7e6: enforce the conversation scope on write tools and stop trusting client-supplied message history in the web adapter

    createChatTools now runs the same scope guard on write tools that read tools already used, so a thread or channel id the model supplies that resolves outside the scoped conversation is rejected before the write executes. sendDirectMessage targets a user id rather than a conversation and stays gated by approval alone.

    The web adapter no longer treats the request body's messages array as a source of conversation state. Only the latest user message is consumed, and tool parts are stripped from it so a browser cannot inject forged tool-call or approval state. Text, file, and custom data parts pass through unchanged; a message left with no parts after stripping is rejected with HTTP 400. Prior turns come from the state adapter when persistMessageHistory is enabled.

  • Updated dependencies [2ce2be0]

  • Updated dependencies [153bd96]

  • Updated dependencies [16ea171]

  • Updated dependencies [eddcd7e]

  • Updated dependencies [bb92688]

  • Updated dependencies [929878b]

  • Updated dependencies [500b7e6]

  • Updated dependencies [b6fa24c]

    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/whatsapp@4.39.0

Patch Changes

  • 3e6e866: support business-scoped user IDs for inbound and outbound WhatsApp messages

  • 7c26965: prevent attachment downloads from sending credentials to untrusted hosts

  • b6fa24c: guard attachment downloads across the remaining adapters

    Slack, Discord, and WhatsApp attachment downloads now go through the shared guarded downloader: private and internal addresses are refused (as URL literals, through DNS resolution, and after redirects), responses are capped at 25 MB, and downloads time out after 30 seconds. Slack sends the bot token only on hops to trusted Slack origins, and WhatsApp keeps its access token on Meta's media hosts and the configured Graph origin. Telegram enforces the same size cap and timeout with the Web Fetch API so downloads keep working in runtimes like Cloudflare Workers.

    downloadAttachment in @chat-adapter/shared now resolves headers per hop (pass a function to control what each redirect target receives), forwards the resolved headers to custom transports, and accepts an onResponse hook to reject unexpected final responses before the body is read.

  • Updated dependencies [2ce2be0]

  • Updated dependencies [153bd96]

  • Updated dependencies [16ea171]

  • Updated dependencies [eddcd7e]

  • Updated dependencies [bb92688]

  • Updated dependencies [929878b]

  • Updated dependencies [500b7e6]

  • Updated dependencies [b6fa24c]

    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/x@4.39.0

Patch Changes

  • Updated dependencies [2ce2be0]
  • Updated dependencies [153bd96]
  • Updated dependencies [16ea171]
  • Updated dependencies [eddcd7e]
  • Updated dependencies [bb92688]
  • Updated dependencies [929878b]
  • Updated dependencies [500b7e6]
  • Updated dependencies [b6fa24c]
    • chat@4.39.0
    • @chat-adapter/shared@4.39.0

@chat-adapter/state-ioredis@4.39.0

Patch Changes

@chat-adapter/state-memory@4.39.0

Patch Changes

@chat-adapter/state-pg@4.39.0

Patch Changes

@chat-adapter/state-redis@4.39.0

Patch Changes

@chat-adapter/tests@4.39.0

@github-actions
github-actions Bot requested a review from a team as a code owner August 18, 2026 14:20
@vercel

vercel Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

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

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

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from d704fcb to bac3fa7 Compare August 18, 2026 15:18
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from bac3fa7 to 77d5698 Compare August 19, 2026 01:16
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 77d5698 to 2ddc1f0 Compare August 20, 2026 00:54
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 2ddc1f0 to 63f9bb5 Compare August 20, 2026 12:35
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 63f9bb5 to 87cdb62 Compare August 24, 2026 10:29
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 87cdb62 to dd304db Compare August 25, 2026 10:12
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from dd304db to 3d3680a Compare August 25, 2026 10:23
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 3d3680a to 5970d81 Compare August 25, 2026 10:52
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5970d81 to 8591568 Compare August 25, 2026 11:10
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 8591568 to 0385c74 Compare August 25, 2026 11:15
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 0385c74 to 7e6c71b Compare August 25, 2026 11:38
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 7e6c71b to 94fdc56 Compare August 27, 2026 00:10
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 94fdc56 to 70ca0f1 Compare August 27, 2026 03:11
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 70ca0f1 to ca49ffb Compare August 27, 2026 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants