Skip to content

fix(types): include bot_id in thread broadcasts - #2769

Open
sean0407 wants to merge 1 commit into
slackapi:mainfrom
sean0407:codex/thread-broadcast-bot-id
Open

sean0407 wants to merge 1 commit into
slackapi:mainfrom
sean0407:codex/thread-broadcast-bot-id

Conversation

@sean0407

Copy link
Copy Markdown

Summary

Fixes #2766 by adding the optional top-level bot_id field to ThreadBroadcastMessageEvent. Thread broadcasts can be authored by users or bots, and root.bot_id describes the parent message rather than the broadcast reply. This lets TypeScript consumers distinguish the reply author correctly.

Validation

  • npm ci --ignore-scripts --no-audit --no-fund — completed in an isolated Node 20 Docker container.
  • npm run build --workspace=@slack/types — passed.
  • npm run test:types --workspace=@slack/types — passed, including a type fixture with top-level bot_id.
  • git diff --check and the project patch policy — passed; 3 files changed, no binary files.

Requirements

@sean0407
sean0407 requested a review from a team as a code owner October 13, 2026 18:00
@changeset-bot

changeset-bot Bot commented Oct 13, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 23acb21

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@slack/types Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@salesforce-cla

Copy link
Copy Markdown

Thanks for the contribution! Before we can merge this, we need @sean0407 to sign the Salesforce Inc. Contributor License Agreement.

This branch has not been deployed

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ThreadBroadcastMessageEvent is missing bot_id

1 participant