chore: release#2569
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
fab77b5 to
397f59f
Compare
Member
2 tasks
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
397f59f to
bbed7eb
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
bbed7eb to
85cb845
Compare
Member
zimeg
approved these changes
Apr 30, 2026
Member
zimeg
left a comment
zimeg
left a comment
There was a problem hiding this comment.
@dependabot Let's get this released! 🚀 ✨
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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/socket-mode@2.0.7
Patch Changes
5395b0c: fix: terminate closing connections earlier if normal close responses fail
If Slack doesn't respond to a close frame, the WebSocket connection is now force-terminated instead of waiting for a response that won't arrive. Since disconnects are expected every few hours, this avoids repeated "pong wasn't received" warnings and speeds up reconnection.