Skip to content

Commit 52abd32

Browse files
chore: release
1 parent 1c95060 commit 52abd32

6 files changed

Lines changed: 14 additions & 20 deletions

.changeset/app-logger-passed-to-receivers.md

Lines changed: 0 additions & 7 deletions
This file was deleted.

.changeset/aws-lambda-node24-handler.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

.changeset/enveloped-event-context-team-id.md

Lines changed: 0 additions & 5 deletions
This file was deleted.

CHANGELOG.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,16 @@
11
# @slack/bolt
22

3+
## 4.7.4
4+
5+
### Patch Changes
6+
7+
- 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.
8+
9+
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.
10+
11+
- 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`.
12+
- 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.
13+
314
## 4.7.3
415

516
### Patch Changes

package-lock.json

Lines changed: 2 additions & 2 deletions
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@slack/bolt",
3-
"version": "4.7.3",
3+
"version": "4.7.4",
44
"description": "A framework for building Slack apps, fast.",
55
"author": "Slack Technologies, LLC",
66
"license": "MIT",

0 commit comments

Comments
 (0)