Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
a60398c to
e09483b
Compare
e09483b to
c750116
Compare
c750116 to
583dbad
Compare
583dbad to
996635e
Compare
996635e to
69fa30e
Compare
69fa30e to
0d4ec3e
Compare
0d4ec3e to
566fd4a
Compare
566fd4a to
6800d9a
Compare
6800d9a to
452e95d
Compare
8e42278 to
5d04596
Compare
5d04596 to
6ce3303
Compare
6ce3303 to
dde5355
Compare
dde5355 to
00916bd
Compare
00916bd to
9a6abc2
Compare
9a6abc2 to
c065f86
Compare
c065f86 to
e761a79
Compare
e761a79 to
e29872e
Compare
e29872e to
ea27445
Compare
ea27445 to
39a59a1
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/discord@4.27.0
Minor Changes
apiUrlconfig option for custom API endpoint configuration (e.g. GovSlack, GitHub Enterprise, GCC-High Teams)Patch Changes
@chat-adapter/gchat@4.27.0
Minor Changes
apiUrlconfig option for custom API endpoint configuration (e.g. GovSlack, GitHub Enterprise, GCC-High Teams)Patch Changes
SelectandRadioSelectcard actions in Google Chat by rendering them asselectionInputwidgets and reading selected values from form inputs on action events.@chat-adapter/github@4.27.0
Minor Changes
apiUrlconfig option for custom API endpoint configuration (e.g. GovSlack, GitHub Enterprise, GCC-High Teams)Patch Changes
@chat-adapter/linear@4.27.0
Minor Changes
6b17c60: Add
apiUrlconfig option for custom API endpoint configuration (e.g. GovSlack, GitHub Enterprise, GCC-High Teams)bc94f0a: Add multi-tenant support in the Linear adapter using
clientId/clientSecret.The Linear adapter now exposes a
handleOAuthCallback()function for OAuth multi-tenant support.Add
clientCredentials.scopesto the Linear adapter so single-tenant client-credentials auth can request custom OAuth scopes.Add support for agent sessions in Linear, with streaming / task / plan support.
Patch Changes
@chat-adapter/slack@4.27.0
Minor Changes
apiUrlconfig option for custom API endpoint configuration (e.g. GovSlack, GitHub Enterprise, GCC-High Teams){ action: "clear" }modal response to close the entire modal view stackPatch Changes
invalid_thread_tsby guarding Slack API calls withthreadTs || undefined@mentionrewrite regex so email addresses (e.g.user@example.com) and<mailto:…>links are no longer mangled into broken Slack user mentions. The lookbehind now excludes any word character before@, which also means mentions immediately following a word character (e.g.prefix@user) are no longer rewritten — a bare@userstill converts as before.@chat-adapter/teams@4.27.0
Minor Changes
apiUrlconfig option for custom API endpoint configuration (e.g. GovSlack, GitHub Enterprise, GCC-High Teams)Patch Changes
@chat-adapter/telegram@4.27.0
Minor Changes
apiUrlconfig option for custom API endpoint configuration (e.g. GovSlack, GitHub Enterprise, GCC-High Teams)Patch Changes
1e7c551: restore attachment fetchData after queue/debounce serialization
b9a1961: Switch Telegram adapter's outbound
parse_modefrom legacyMarkdowntoMarkdownV2, and replace the standard-markdown passthrough renderer with a proper AST → MarkdownV2 renderer. Standard markdown (**bold**) and legacyMarkdown(*bold*) use different syntaxes and have no shared escape rules, so any message containing.,!,(,),-,_in regular text — which is virtually every LLM-generated message — was being rejected withcan't parse entities. The new renderer walks the mdast tree and emits MarkdownV2 with context-aware escaping (normal text vs. code blocks vs. link URLs), uniformly applies MarkdownV2parse_modeto every format-converter output (including AST messages, which previously shipped withoutparse_modeand rendered asterisks literally), and escapes card fallback text.Also fix silent message truncation that the MarkdownV2 migration widened from a rare bug into a reliable 400. The previous truncator sliced messages at 4096/1024 chars and appended literal
..., but in MarkdownV2.is a reserved character that must be escaped, the slice can leave an orphan trailing\, and it can cut through a paired entity (*bold*,`code`) leaving it unclosed — all of which causecan't parse entities. The two truncate methods are unified intotruncateForTelegram(text, limit, parseMode), which appends an escaped\.\.\.for MarkdownV2 and walks back past unbalanced entity delimiters or orphan backslashes before appending. Plain-text messages keep literal....Internal typing hardening:
renderMarkdownV2is now typed exhaustively on mdast'sNodesunion with aneverassertion, so new mdast node types fail the build rather than silently falling through. IntroduceTelegramParseMode = "MarkdownV2" | "plain"replacing the previousstring | undefinedat call sites, withtoBotApiParseModemapping to the Bot API wire format at the boundary. Thechatpackage gains a re-export of mdast'sNodesunion so adapters can build exhaustively typed renderers without importing mdast directly.Updated dependencies [1e7c551]
Updated dependencies [b9a1961]
Updated dependencies [9093292]
Updated dependencies [7e90d9c]
Updated dependencies [bca4792]
Updated dependencies [37dbb4a]
Updated dependencies [608d5f0]
Updated dependencies [a179b29]
Updated dependencies [a8f2aab]
@chat-adapter/whatsapp@4.27.0
Minor Changes
apiUrlconfig option for custom API endpoint configuration (e.g. GovSlack, GitHub Enterprise, GCC-High Teams)Patch Changes
chat@4.27.0
Minor Changes
1e7c551: restore attachment fetchData after queue/debounce serialization
b9a1961: Switch Telegram adapter's outbound
parse_modefrom legacyMarkdowntoMarkdownV2, and replace the standard-markdown passthrough renderer with a proper AST → MarkdownV2 renderer. Standard markdown (**bold**) and legacyMarkdown(*bold*) use different syntaxes and have no shared escape rules, so any message containing.,!,(,),-,_in regular text — which is virtually every LLM-generated message — was being rejected withcan't parse entities. The new renderer walks the mdast tree and emits MarkdownV2 with context-aware escaping (normal text vs. code blocks vs. link URLs), uniformly applies MarkdownV2parse_modeto every format-converter output (including AST messages, which previously shipped withoutparse_modeand rendered asterisks literally), and escapes card fallback text.Also fix silent message truncation that the MarkdownV2 migration widened from a rare bug into a reliable 400. The previous truncator sliced messages at 4096/1024 chars and appended literal
..., but in MarkdownV2.is a reserved character that must be escaped, the slice can leave an orphan trailing\, and it can cut through a paired entity (*bold*,`code`) leaving it unclosed — all of which causecan't parse entities. The two truncate methods are unified intotruncateForTelegram(text, limit, parseMode), which appends an escaped\.\.\.for MarkdownV2 and walks back past unbalanced entity delimiters or orphan backslashes before appending. Plain-text messages keep literal....Internal typing hardening:
renderMarkdownV2is now typed exhaustively on mdast'sNodesunion with aneverassertion, so new mdast node types fail the build rather than silently falling through. IntroduceTelegramParseMode = "MarkdownV2" | "plain"replacing the previousstring | undefinedat call sites, withtoBotApiParseModemapping to the Bot API wire format at the boundary. Thechatpackage gains a re-export of mdast'sNodesunion so adapters can build exhaustively typed renderers without importing mdast directly.9093292: add streaming options to thread.post() with platform-specific namespacing
7e90d9c: Add Socket Mode support for environments behind firewalls that can't expose public HTTP endpoints, and add
{ action: "clear" }modal response to close the entire modal view stackbca4792: Allow
task_updatestreaming chunks to include optionaldetailstext for Slack task cards37dbb4a: Add
thread.getParticipants()to get unique human participants in a thread608d5f0: Add
chat.thread(threadId)method to create Thread handles outside of webhook contextsa179b29: Implement external_select block kit for Slack
a8f2aab: Allow
plan.updateTask()to target a specific task by ID via{ id: taskId }instead of always updating the last in_progress task@chat-adapter/shared@4.27.0
Patch Changes
@chat-adapter/state-ioredis@4.27.0
Patch Changes
@chat-adapter/state-memory@4.27.0
Patch Changes
@chat-adapter/state-pg@4.27.0
Patch Changes
@chat-adapter/state-redis@4.27.0
Patch Changes