chore: release

docs/english/reference/socket-mode/classes/SocketModeClient.md

@@ -116,7 +116,7 @@ EventEmitter.addListener
 disconnect(): Promise<void>;
 ```
 
-Defined in: [packages/socket-mode/src/SocketModeClient.ts:221](https://github.com/slackapi/node-slack-sdk/blob/main/packages/socket-mode/src/SocketModeClient.ts#L221)
+Defined in: [packages/socket-mode/src/SocketModeClient.ts:223](https://github.com/slackapi/node-slack-sdk/blob/main/packages/socket-mode/src/SocketModeClient.ts#L223)
 
 End a Socket Mode session. After this method is called no messages will be sent or received
 unless you call start() again later.
@@ -472,7 +472,7 @@ EventEmitter.removeListener
 start(): Promise<AppsConnectionsOpenResponse>;
 ```
 
-Defined in: [packages/socket-mode/src/SocketModeClient.ts:178](https://github.com/slackapi/node-slack-sdk/blob/main/packages/socket-mode/src/SocketModeClient.ts#L178)
+Defined in: [packages/socket-mode/src/SocketModeClient.ts:180](https://github.com/slackapi/node-slack-sdk/blob/main/packages/socket-mode/src/SocketModeClient.ts#L180)
 
 Start a Socket Mode session app.
 This method must be called before any messages can be sent or received,

docs/english/reference/socket-mode/index.md

@@ -1,4 +1,4 @@
-# @slack/socket-mode v3.0.0
+# @slack/socket-mode v3.0.1
 
 ## Enumerations
 

packages/socket-mode/CHANGELOG.md

@@ -1,5 +1,15 @@
 # @slack/socket-mode
 
+## 3.0.1
+
+### Patch Changes
+
+- 5c2362c: Fix leaked TCP sockets on disconnect ([#2709](https://github.com/slackapi/node-slack-sdk/issues/2709)). Moving from `ws` to undici's `WebSocket` in 3.0.0 dropped every force-close mechanism, so `ESTABLISHED` sockets were never torn down and accumulated toward Slack's per-app connection cap.
+
+  - `disconnect()` now arms a 30s close-handshake timeout, so a peer that never replies to the close frame no longer leaves the socket stuck in `CLOSING` indefinitely.
+  - On the default dispatcher path, the underlying TCP socket is now captured and force-destroyed during cleanup. A user-supplied `dispatcher` owns its own socket and instead relies on the close-handshake timeout — this limitation is documented on the `dispatcher` option.
+  - The `close` handler no longer schedules a reconnect on stale or overlapping close events, so at most one reconnect is scheduled per disconnect.
+
 ## 3.0.0
 
 ### Major Changes

packages/socket-mode/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@slack/socket-mode",
-  "version": "3.0.0",
+  "version": "3.0.1",
   "description": "Official library for using the Slack Platform's Socket Mode API",
   "author": "Slack Technologies, LLC",
   "license": "MIT",