chore: release #2720

Merged
github-actions[bot] opened 2:27pm on August 27, 2026 wanted to merge 1 commit into slackapi/node-slack-sdk main from
changeset-release/main

Pull Request Overview

  • Opened on August 27, 2026
  • Status Merged
  • Commit count 1 with first commit August 27, 2026

Total Delta

0 Total Diff Delta

Open Days

Open 17 weekdays

Test Delta

0 Diff Delta in Test Files
Breakdown by Phase

How long has this pull request spent in each phase of its lifecycle?

Fraction of total time Business days Phase
 
0.0 days Authoring 0 commits before pull request opened for review
 
0.0 days Awaiting first review
Set up deploy tracking to begin tracking full PR start-to-deploy times

Total time for pull request 0.0 business days from first commit authored to merge
Deploy tracking has not been set up

Author avatar

chore: release

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@slack/[email protected]

Patch Changes



  • 5c2362c: Fix leaked TCP sockets on disconnect (#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.



Comments Threads Pending Resolution

Resolved Comment Threads

No resolved comments have been left on this PR.