diff --git a/.changeset/app-logger-passed-to-receivers.md b/.changeset/app-logger-passed-to-receivers.md
deleted file mode 100644
index dc30db29a..000000000
--- a/.changeset/app-logger-passed-to-receivers.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"@slack/bolt": patch
----
-
-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.
diff --git a/.changeset/aws-lambda-node24-handler.md b/.changeset/aws-lambda-node24-handler.md
deleted file mode 100644
index 8ef1a7161..000000000
--- a/.changeset/aws-lambda-node24-handler.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@slack/bolt": patch
----
-
-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`.
diff --git a/.changeset/enveloped-event-context-team-id.md b/.changeset/enveloped-event-context-team-id.md
deleted file mode 100644
index ee3aebf29..000000000
--- a/.changeset/enveloped-event-context-team-id.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"@slack/bolt": patch
----
-
-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.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 676b538ad..e5aa17693 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -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
diff --git a/package-lock.json b/package-lock.json
index 50a5d9218..55a8089d3 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,12 +1,12 @@
 {
   "name": "@slack/bolt",
-  "version": "4.7.3",
+  "version": "4.7.4",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "@slack/bolt",
-      "version": "4.7.3",
+      "version": "4.7.4",
       "license": "MIT",
       "dependencies": {
         "@slack/logger": "^4.0.1",
diff --git a/package.json b/package.json
index aa178789f..f6b5ca0b2 100644
--- a/package.json
+++ b/package.json
@@ -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",