Skip to content

chore(release): version packages - #907

Merged
dancer merged 1 commit into
mainfrom
changeset-release/main
Sep 18, 2026
Merged

chore(release): version packages#907
dancer merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 6, 2026 •
edited
Loading

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/discord@4.41.0

Minor Changes

  • 61b98fc: Update discord-api-types from 0.37 to 0.38 and use its types for every Discord payload instead of hand-written copies. DiscordComponentType and DiscordMessageFlag keep their plain as const shape and member set; their values now come from ComponentType and MessageFlags.

    Type changes for TypeScript consumers of DiscordInteractionFlagsContext: interaction is now APIApplicationCommandInteraction and user is APIUser, so user.avatar and user.global_name are string | null instead of optional strings. Context menu commands continue to reach onSlashCommand under their command name.

    Gateway forwarding fixes for reactions: the forwarder now sets channel_type, the resolved thread for reactions posted in threads, and the reacting user for DM reactions, so the webhook side resolves threads and DM reactors without a second channel lookup. Events for the same channel are forwarded in the order the Gateway delivered them, so a quick add-then-remove no longer races. Failed channel or user lookups during forwarding are logged at warn instead of being dropped silently.

    Legacy Gateway mode no longer fails slash commands and button clicks in channels discord.js has not cached (for example a first DM); the handlers fall back to channel_id as before.

Patch Changes

  • fcdc1c9: Honor an adapter's definitive isMention: false instead of re-detecting mentions from the message text.

    An adapter that reads structured platform content reports true or false, and the SDK falls back to matching @username in the text only when the adapter reports nothing. A definitive false now wins, so an adapter can suppress a mention that exists only in text its platform renders literally, such as a code sample. Adapters that previously returned false to mean "not detected" should return undefined instead. Direct messages are unchanged: with no onDirectMessage handler registered they still route to onNewMention.

    Adapter changes that follow from the new contract:

    • Linear: ordinary comments are left undetermined, so SDK text detection still applies to them.
    • Notion: keyword mode leaves comments without a keyword match undetermined instead of reporting false, so @userName in the text still counts.
    • X: posts rebuilt from raw or fetched by id are left undetermined instead of reporting false. Only post.mention.create events report true.
    • Discord: a real ping, role mention, @everyone, or allowlisted channel reports true; anything else is left undetermined instead of false, so a literal @botname typed in the text still counts as before.

  • Updated dependencies [f233ffe]

  • Updated dependencies [6adca36]

  • Updated dependencies [ad90432]

  • Updated dependencies [683eadc]

  • Updated dependencies [dc2a777]

  • Updated dependencies [139d337]

  • Updated dependencies [2e2426d]

  • Updated dependencies [8421953]

  • Updated dependencies [91683e5]

  • Updated dependencies [056d883]

  • Updated dependencies [c21ccbc]

  • Updated dependencies [fcdc1c9]

    • chat@4.41.0
    • @chat-adapter/shared@4.41.0

@chat-adapter/gmail@4.41.0

Minor Changes

  • bfee00a: add Gmail email handoff and threaded replies with standalone API, MIME and webhook primitives

Patch Changes

@chat-adapter/slack@4.41.0

Minor Changes

  • ad90432: Add opt-in selection change events for Select and RadioSelect inputs in Slack modals
  • 6adca36: Support Slack egress proxies across Socket Mode, response URLs, webhook forwarding, and guarded file downloads with adapter-scoped transport options.

Patch Changes

  • 683eadc: Read the bot's mention from the message content instead of trusting the app_mention event type.

    Slack can deliver app_mention for a message whose bot-id reference only appears inside code, where it renders literally and is not an invocation. The adapter now classifies the content the way Slack renders it: a user element for the bot, or a <@U…> token in mrkdwn content, is a mention. Inline code (style.code), preformatted elements, rich-text text elements, link labels, and raw_text table cells render literally and are not mentions.

    When a message carries blocks, they model its body and the flattened text field is not consulted, because it loses the code/literal distinction. A message whose content was inspected and holds no mention reports isMention: false, even when the bot's display name appears as plain text. The synchronous parseMessage path classifies the same way, so the pre-edit snapshot of an edited message agrees with the edited message.

    An app_mention event whose content never shows the known bot id is still trusted, because Slack saw a mention under an id the adapter does not know (for example the W… id an Enterprise Grid workspace emits). When the adapter cannot identify the bot at all (botUserId unresolved), app_mention is trusted the same way and other messages stay undetermined.

    raw_text table cells now render literally, matching how they are classified: Slack reserves mentions and links for rich_text cells, so a <@U…> token in a raw_text cell no longer resolves to a display name.

  • c21ccbc: Add an opt-in webhook option to propagate message, action, and slash command handler errors through waitUntil while preserving default behavior.

  • Updated dependencies [f233ffe]

  • Updated dependencies [6adca36]

  • Updated dependencies [ad90432]

  • Updated dependencies [683eadc]

  • Updated dependencies [dc2a777]

  • Updated dependencies [139d337]

  • Updated dependencies [2e2426d]

  • Updated dependencies [8421953]

  • Updated dependencies [91683e5]

  • Updated dependencies [056d883]

  • Updated dependencies [c21ccbc]

  • Updated dependencies [fcdc1c9]

    • chat@4.41.0
    • @chat-adapter/shared@4.41.0

@chat-adapter/teams@4.41.0

Minor Changes

  • 139d337: Support Vercel Connect in the Teams adapter with lazy app identity resolution and custom webhook verification. Ensure custom Bot Framework and Graph token factories take precedence over client-secret environment variables.

    Add Teams to create-chat-sdk --connect and interactive Connect scaffolding, including the helper, connector environment variable, and setup documentation.

  • 2e2426d: Add onInstalled and onUninstalled handlers for installation lifecycle events. The Teams adapter emits them for installationUpdate activities, including the add-upgrade and remove-upgrade actions, with a persistable channelId for later proactive messages.

    The Teams adapter now sends, edits, deletes, reacts, and types against the service URL encoded in the thread ID instead of the app-wide default, so conversations hosted on regional or sovereign Bot Framework endpoints are reached correctly. An explicit apiUrl still pins every call to that endpoint.

  • 8421953: feat(teams): render tables as the Adaptive Card 1.5 Table element

    The Teams adapter now renders Table as the native Adaptive Cards Table element instead of a Container of ColumnSets. Teams draws grid lines between cells, sizes columns by relative weight and marks the header row for accessibility. The @chat-adapter/teams/cards subpath emits the same element.

    Table gains optional rendering options that only Teams reads: widths (positive integer column weights), verticalAlign (vertical alignment of cell content), gridLines (default true) and gridStyle. Other adapters ignore them. Pass gridLines: false to keep a borderless table.

    The chat JSX runtime now forwards align on <Table>, matching fromReactElement.

Patch Changes

  • 8508903: Edit and delete Microsoft Teams targeted messages through the ?isTargetedActivity=true endpoint, so a message sent with postEphemeral can be updated or removed instead of failing with 400 Bad argument. The ids sent targeted are recorded in the Chat state adapter with a 24-hour TTL, matching how long Teams keeps a targeted message.
  • 91683e5: Wait for Telegram polling handlers to settle before advancing update offsets.
  • c21ccbc: Add an opt-in webhook option to propagate message, action, and slash command handler errors through waitUntil while preserving default behavior.
  • Updated dependencies [f233ffe]
  • Updated dependencies [6adca36]
  • Updated dependencies [ad90432]
  • Updated dependencies [683eadc]
  • Updated dependencies [dc2a777]
  • Updated dependencies [139d337]
  • Updated dependencies [2e2426d]
  • Updated dependencies [8421953]
  • Updated dependencies [91683e5]
  • Updated dependencies [056d883]
  • Updated dependencies [c21ccbc]
  • Updated dependencies [fcdc1c9]
    • chat@4.41.0
    • @chat-adapter/shared@4.41.0

chat@4.41.0

Minor Changes

  • ad90432: Add opt-in selection change events for Select and RadioSelect inputs in Slack modals

  • dc2a777: Add TanStack AI support. thread.post(), thread.reply(), and channel.post() accept the stream returned by TanStack's chat(), and the new chat/ai/tanstack subpath provides toTanStackMessages for thread history and createTanStackTools for the Chat SDK toolset. Neither adds a runtime dependency on @tanstack/ai; the tools require zod 4.2 or newer.

  • 139d337: Support Vercel Connect in the Teams adapter with lazy app identity resolution and custom webhook verification. Ensure custom Bot Framework and Graph token factories take precedence over client-secret environment variables.

    Add Teams to create-chat-sdk --connect and interactive Connect scaffolding, including the helper, connector environment variable, and setup documentation.

  • 2e2426d: Add onInstalled and onUninstalled handlers for installation lifecycle events. The Teams adapter emits them for installationUpdate activities, including the add-upgrade and remove-upgrade actions, with a persistable channelId for later proactive messages.

    The Teams adapter now sends, edits, deletes, reacts, and types against the service URL encoded in the thread ID instead of the app-wide default, so conversations hosted on regional or sovereign Bot Framework endpoints are reached correctly. An explicit apiUrl still pins every call to that endpoint.

  • 8421953: feat(teams): render tables as the Adaptive Card 1.5 Table element

    The Teams adapter now renders Table as the native Adaptive Cards Table element instead of a Container of ColumnSets. Teams draws grid lines between cells, sizes columns by relative weight and marks the header row for accessibility. The @chat-adapter/teams/cards subpath emits the same element.

    Table gains optional rendering options that only Teams reads: widths (positive integer column weights), verticalAlign (vertical alignment of cell content), gridLines (default true) and gridStyle. Other adapters ignore them. Pass gridLines: false to keep a borderless table.

    The chat JSX runtime now forwards align on <Table>, matching fromReactElement.

  • 056d883: Allow history.user.maxPerUser and legacy transcripts.maxPerUser to be false to disable count-based history eviction. The default remains 200 entries per user.

  • fcdc1c9: Honor an adapter's definitive isMention: false instead of re-detecting mentions from the message text.

    An adapter that reads structured platform content reports true or false, and the SDK falls back to matching @username in the text only when the adapter reports nothing. A definitive false now wins, so an adapter can suppress a mention that exists only in text its platform renders literally, such as a code sample. Adapters that previously returned false to mean "not detected" should return undefined instead. Direct messages are unchanged: with no onDirectMessage handler registered they still route to onNewMention.

    Adapter changes that follow from the new contract:

    • Linear: ordinary comments are left undetermined, so SDK text detection still applies to them.
    • Notion: keyword mode leaves comments without a keyword match undetermined instead of reporting false, so @userName in the text still counts.
    • X: posts rebuilt from raw or fetched by id are left undetermined instead of reporting false. Only post.mention.create events report true.
    • Discord: a real ping, role mention, @everyone, or allowlisted channel reports true; anything else is left undetermined instead of false, so a literal @botname typed in the text still counts as before.

Patch Changes

  • f233ffe: Retry initialization after a failed state connection. Once the state adapter (for example Redis) recovers, the next initialize() call or webhook tries again instead of rejecting with the original connection error. Concurrent callers still share one attempt. Adapter initialization failures remain cached until shutdown() so retries cannot restart adapters that are already running or still starting.
  • 91683e5: Wait for Telegram polling handlers to settle before advancing update offsets.
  • c21ccbc: Add an opt-in webhook option to propagate message, action, and slash command handler errors through waitUntil while preserving default behavior.

create-chat-sdk@0.5.0

Minor Changes

  • 961cf45: Generate Linear Connect bots with explicit agent-session mode and setup guidance. Recommend agent sessions once during initialization when a token resolver and webhook verifier are configured without a mode, while preserving the adapter's comments default.

  • 139d337: Support Vercel Connect in the Teams adapter with lazy app identity resolution and custom webhook verification. Ensure custom Bot Framework and Graph token factories take precedence over client-secret environment variables.

    Add Teams to create-chat-sdk --connect and interactive Connect scaffolding, including the helper, connector environment variable, and setup documentation.

Patch Changes

  • 1136c96: Tailor generated README setup instructions to Connect-forwarded and native webhooks, including projects that use both.

@chat-adapter/state-pg@4.41.0

Minor Changes

  • ea025af: Add autoCreateSchema to let applications provision PostgreSQL state tables and indexes through migrations. With autoCreateSchema: false, connect() issues no DDL and instead verifies that the tables and grants exist, rejecting with a descriptive error rather than failing on the first message. The complete DDL is exported as postgresSchemaStatements for migration tooling.

Patch Changes

@chat-adapter/tests@4.41.0

Minor Changes

  • 2e2426d: Add onInstalled and onUninstalled handlers for installation lifecycle events. The Teams adapter emits them for installationUpdate activities, including the add-upgrade and remove-upgrade actions, with a persistable channelId for later proactive messages.

    The Teams adapter now sends, edits, deletes, reacts, and types against the service URL encoded in the thread ID instead of the app-wide default, so conversations hosted on regional or sovereign Bot Framework endpoints are reached correctly. An explicit apiUrl still pins every call to that endpoint.

@chat-adapter/gchat@4.41.0

Patch Changes

  • d634346: editMessage, deleteMessage, addReaction, and removeReaction now require the message id to be a well-formed spaces/{space}/messages/{message} resource name in the thread's space before calling the Google Chat API. Message ids identify a message on their own, so a permitted thread id could previously be paired with a message from another space, including names that only resolved there after path normalization. The adapter also gains fetchMessage(), which returns a message with the thread Google reports for it.
  • Updated dependencies [f233ffe]
  • Updated dependencies [6adca36]
  • Updated dependencies [ad90432]
  • Updated dependencies [683eadc]
  • Updated dependencies [dc2a777]
  • Updated dependencies [139d337]
  • Updated dependencies [2e2426d]
  • Updated dependencies [8421953]
  • Updated dependencies [91683e5]
  • Updated dependencies [056d883]
  • Updated dependencies [c21ccbc]
  • Updated dependencies [fcdc1c9]
    • chat@4.41.0
    • @chat-adapter/shared@4.41.0

@chat-adapter/github@4.41.0

Patch Changes

@chat-adapter/instagram@4.41.0

Patch Changes

@chat-adapter/linear@4.41.0

Patch Changes

  • 961cf45: Generate Linear Connect bots with explicit agent-session mode and setup guidance. Recommend agent sessions once during initialization when a token resolver and webhook verifier are configured without a mode, while preserving the adapter's comments default.

  • fcdc1c9: Honor an adapter's definitive isMention: false instead of re-detecting mentions from the message text.

    An adapter that reads structured platform content reports true or false, and the SDK falls back to matching @username in the text only when the adapter reports nothing. A definitive false now wins, so an adapter can suppress a mention that exists only in text its platform renders literally, such as a code sample. Adapters that previously returned false to mean "not detected" should return undefined instead. Direct messages are unchanged: with no onDirectMessage handler registered they still route to onNewMention.

    Adapter changes that follow from the new contract:

    • Linear: ordinary comments are left undetermined, so SDK text detection still applies to them.
    • Notion: keyword mode leaves comments without a keyword match undetermined instead of reporting false, so @userName in the text still counts.
    • X: posts rebuilt from raw or fetched by id are left undetermined instead of reporting false. Only post.mention.create events report true.
    • Discord: a real ping, role mention, @everyone, or allowlisted channel reports true; anything else is left undetermined instead of false, so a literal @botname typed in the text still counts as before.

  • Updated dependencies [f233ffe]

  • Updated dependencies [6adca36]

  • Updated dependencies [ad90432]

  • Updated dependencies [683eadc]

  • Updated dependencies [dc2a777]

  • Updated dependencies [139d337]

  • Updated dependencies [2e2426d]

  • Updated dependencies [8421953]

  • Updated dependencies [91683e5]

  • Updated dependencies [056d883]

  • Updated dependencies [c21ccbc]

  • Updated dependencies [fcdc1c9]

    • chat@4.41.0
    • @chat-adapter/shared@4.41.0

@chat-adapter/messenger@4.41.0

Patch Changes

@chat-adapter/notion@4.41.0

Patch Changes

  • fcdc1c9: Honor an adapter's definitive isMention: false instead of re-detecting mentions from the message text.

    An adapter that reads structured platform content reports true or false, and the SDK falls back to matching @username in the text only when the adapter reports nothing. A definitive false now wins, so an adapter can suppress a mention that exists only in text its platform renders literally, such as a code sample. Adapters that previously returned false to mean "not detected" should return undefined instead. Direct messages are unchanged: with no onDirectMessage handler registered they still route to onNewMention.

    Adapter changes that follow from the new contract:

    • Linear: ordinary comments are left undetermined, so SDK text detection still applies to them.
    • Notion: keyword mode leaves comments without a keyword match undetermined instead of reporting false, so @userName in the text still counts.
    • X: posts rebuilt from raw or fetched by id are left undetermined instead of reporting false. Only post.mention.create events report true.
    • Discord: a real ping, role mention, @everyone, or allowlisted channel reports true; anything else is left undetermined instead of false, so a literal @botname typed in the text still counts as before.

  • Updated dependencies [f233ffe]

  • Updated dependencies [6adca36]

  • Updated dependencies [ad90432]

  • Updated dependencies [683eadc]

  • Updated dependencies [dc2a777]

  • Updated dependencies [139d337]

  • Updated dependencies [2e2426d]

  • Updated dependencies [8421953]

  • Updated dependencies [91683e5]

  • Updated dependencies [056d883]

  • Updated dependencies [c21ccbc]

  • Updated dependencies [fcdc1c9]

    • chat@4.41.0
    • @chat-adapter/shared@4.41.0

@chat-adapter/shared@4.41.0

Patch Changes

  • 6adca36: Enforce the guarded download deadline inside downloadAttachment itself, for both the wait for response headers and the body read. A late response is destroyed, so the timeout holds even when a custom transport ignores the supplied signal.
  • 683eadc: Add maskCodeSpans, which blanks inline code spans and fenced code blocks using the same scanner as replaceBareMentions, so adapters can classify a mention token while ignoring the ones inside code.
  • Updated dependencies [f233ffe]
  • Updated dependencies [ad90432]
  • Updated dependencies [dc2a777]
  • Updated dependencies [139d337]
  • Updated dependencies [2e2426d]
  • Updated dependencies [8421953]
  • Updated dependencies [91683e5]
  • Updated dependencies [056d883]
  • Updated dependencies [c21ccbc]
  • Updated dependencies [fcdc1c9]
    • chat@4.41.0

@chat-adapter/telegram@4.41.0

Patch Changes

  • f893470: Stop cutting Telegram MarkdownV2 messages and captions at a backtick inside a link destination. Messages that fit the length limit now ship exactly as rendered, and a length cut that lands inside a link, code span, or underline now removes the incomplete entity before the ellipsis.
  • 91683e5: Wait for Telegram polling handlers to settle before advancing update offsets.
  • Updated dependencies [f233ffe]
  • Updated dependencies [6adca36]
  • Updated dependencies [ad90432]
  • Updated dependencies [683eadc]
  • Updated dependencies [dc2a777]
  • Updated dependencies [139d337]
  • Updated dependencies [2e2426d]
  • Updated dependencies [8421953]
  • Updated dependencies [91683e5]
  • Updated dependencies [056d883]
  • Updated dependencies [c21ccbc]
  • Updated dependencies [fcdc1c9]
    • chat@4.41.0
    • @chat-adapter/shared@4.41.0

@chat-adapter/twilio@4.41.0

Patch Changes

@chat-adapter/web@4.41.0

Patch Changes

@chat-adapter/whatsapp@4.41.0

Patch Changes

@chat-adapter/x@4.41.0

Patch Changes

  • fcdc1c9: Honor an adapter's definitive isMention: false instead of re-detecting mentions from the message text.

    An adapter that reads structured platform content reports true or false, and the SDK falls back to matching @username in the text only when the adapter reports nothing. A definitive false now wins, so an adapter can suppress a mention that exists only in text its platform renders literally, such as a code sample. Adapters that previously returned false to mean "not detected" should return undefined instead. Direct messages are unchanged: with no onDirectMessage handler registered they still route to onNewMention.

    Adapter changes that follow from the new contract:

    • Linear: ordinary comments are left undetermined, so SDK text detection still applies to them.
    • Notion: keyword mode leaves comments without a keyword match undetermined instead of reporting false, so @userName in the text still counts.
    • X: posts rebuilt from raw or fetched by id are left undetermined instead of reporting false. Only post.mention.create events report true.
    • Discord: a real ping, role mention, @everyone, or allowlisted channel reports true; anything else is left undetermined instead of false, so a literal @botname typed in the text still counts as before.

  • Updated dependencies [f233ffe]

  • Updated dependencies [6adca36]

  • Updated dependencies [ad90432]

  • Updated dependencies [683eadc]

  • Updated dependencies [dc2a777]

  • Updated dependencies [139d337]

  • Updated dependencies [2e2426d]

  • Updated dependencies [8421953]

  • Updated dependencies [91683e5]

  • Updated dependencies [056d883]

  • Updated dependencies [c21ccbc]

  • Updated dependencies [fcdc1c9]

    • chat@4.41.0
    • @chat-adapter/shared@4.41.0

@chat-adapter/state-ioredis@4.41.0

Patch Changes

@chat-adapter/state-memory@4.41.0

Patch Changes

@chat-adapter/state-redis@4.41.0

Patch Changes

@github-actions
github-actions Bot requested a review from a team as a code owner September 6, 2026 05:34
@vercel

vercel Bot commented Sep 6, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

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

Project Deployment Actions Updated
chat Ready Ready Preview, v0 Sep 18, 2026 9:41am UTC
chat-sdk-nextjs-chat Ready Ready Preview, v0 Sep 18, 2026 9:41am UTC

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 729a91a to 0d3ca77 Compare September 9, 2026 17:25
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 0d3ca77 to 485ff12 Compare September 9, 2026 17:38
@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Your Vercel team Vercel Labs is not permitted to deploy from this git repository. Contact an administrator to add github organization vercel as a Protected Git Scope in Vercel Labs on Vercel. Once added, commit again to see your changes.

Learn more: https://vercel.com/docs/security/protected-git-scopes

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 485ff12 to 34310df Compare September 9, 2026 17:46
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 34310df to 21c88d7 Compare September 9, 2026 17:54
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 21c88d7 to f49f656 Compare September 16, 2026 00:15
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from f49f656 to b577a44 Compare September 16, 2026 00:20
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from b577a44 to 1d2447f Compare September 16, 2026 00:26
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 1d2447f to a7c38e0 Compare September 16, 2026 00:32
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from a7c38e0 to c022698 Compare September 16, 2026 00:41
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from c022698 to 090fb20 Compare September 16, 2026 20:23
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 0806270 to ad19a16 Compare September 17, 2026 15:09
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from ad19a16 to eb99e63 Compare September 17, 2026 20:20
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 5676d4e to a8ef263 Compare September 18, 2026 04:43
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from a8ef263 to 0b1b596 Compare September 18, 2026 09:39
@dancer
dancer merged commit dd8e9b9 into main Sep 18, 2026
19 checks passed
@dancer
dancer deleted the changeset-release/main branch September 18, 2026 12:29

This branch was successfully deployed

2 active deployments
Preview – chat — 0b1b5969 Deployed Sep 18, 2026 by vercel[bot]
View deployment
Preview – chat-sdk-nextjs-chat — 0b1b5969 Deployed Sep 18, 2026 by vercel[bot]
View deployment
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@dancer dancer dancer approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@dancer