Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 0 additions & 7 deletions .changeset/app-logger-passed-to-receivers.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/aws-lambda-node24-handler.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/enveloped-event-context-team-id.md

This file was deleted.

11 changes: 11 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,16 @@
# @slack/bolt

## 4.7.4

### Patch Changes

- 9839a50: Pass the App's named `bolt-app` `ConsoleLogger` to the default receivers when no `logger` option is provided. Previously the App constructor built a named logger on `this.logger` but threaded the raw (potentially undefined) constructor argument into `initReceiver`, so `HTTPReceiver` / `SocketModeReceiver` each built their own anonymous logger and receiver-side log lines (e.g. unhandled HTTP requests on custom routes) appeared without the `bolt-app` prefix.

Behaviour change for the no-`logger` case: the default receiver now shares the same `Logger` instance as `app.logger`, so a downstream `app.logger.setLevel(...)` after construction will affect receiver-side logging too. This is consistent with the existing behaviour that already mutates `this.logger`'s level via the `logLevel` constructor option. Apps that supplied their own `logger` are unaffected; apps that relied on the receiver's logger being independent of `app.logger` will need to pass a separate `logger` into the receiver explicitly.

- e1c21d7: Fix `AwsLambdaReceiver.toHandler()` so Bolt apps on the AWS Lambda Node.js 24+ runtime no longer fail at startup with `Runtime.CallbackHandlerDeprecated`. The returned handler is now a 2-arg promise-based function; the unused trailing `callback` parameter has been removed from the `AwsHandler` type. The legacy `AwsCallback` export is retained and marked `@deprecated`.
- f2de079: Add `context_team_id` and `context_enterprise_id` as optional fields on the `EnvelopedEvent` type. Slack's Events API delivers these on the envelope for Slack Connect channels and Enterprise Grid org-wide apps, where `team_id` may refer to a workspace different from the one the bot is installed in. Without the typed fields, downstream code had to reach for `@ts-expect-error` or unsafe casts to route by the correct workspace.

## 4.7.3

### Patch Changes
Expand Down
4 changes: 2 additions & 2 deletions package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "@slack/bolt",
"version": "4.7.3",
"version": "4.7.4",
"description": "A framework for building Slack apps, fast.",
"author": "Slack Technologies, LLC",
"license": "MIT",
Expand Down