Bump @slack/bolt to ^5.0.0#48837
Merged
Merged
Conversation
Deploy previewBundle size
Check out the code infra dashboard for more information about this PR. |
code-infra-renovate
Bot
force-pushed
the
renovate/slack-bolt-5.x
branch
from
July 20, 2026 07:21
44db27d to
a4c7499
Compare
ZeeshanTamboli
approved these changes
Jul 20, 2026
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
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 contains the following updates:
^4.7.3→^5.0.0Release Notes
slackapi/bolt-js (@slack/bolt)
v5.0.0Compare Source
Major Changes
d284e69: Drop Node.js 18 support. The minimum required runtime is now Node.js 20 (npm >=9.6.4).d284e69: Remove deprecatedWorkflowStepclass and all associated types, middleware, and utilities. UseCustomFunctionandapp.function()instead.d284e69: Replace axios with native fetch for response_url calls. RemoveagentandclientTlsoptions fromAppOptions— useclientOptions.fetchto provide a custom fetch implementation for proxy/TLS needs. Add adispatcheroption toSocketModeReceiverfor proxy/TLS configuration in socket mode.respond()now throws aRespondErrorwhen theresponse_urlrequest returns a non-2xx status (restoring the throw-on-failure behavior that axios provided) and resolves to aResponseon success rather than an axios response object.Minor Changes
d284e69: Improve error handling by leveraging@slack/web-apiv8 error classes. Authorization errors are now properly wrapped in anAuthorizationError, preserving the original thrown value (non-Errorrejections are retained via thecauseof the wrapped original). Default error handlers log richer details for web-api errors (API error codes, rate limit durations, HTTP status codes) alongside the full error object, so stack traces and causes remain available. The@slack/web-apierror classes (SlackError,WebAPIPlatformError,WebAPIRequestError,WebAPIHTTPError,WebAPIRateLimitedError) can be imported from@slack/web-apiforinstanceofchecks.Patch Changes
9839a50: Pass the App's namedbolt-appConsoleLoggerto the default receivers when nologgeroption is provided. Previously the App constructor built a named logger onthis.loggerbut threaded the raw (potentially undefined) constructor argument intoinitReceiver, soHTTPReceiver/SocketModeReceivereach built their own anonymous logger and receiver-side log lines (e.g. unhandled HTTP requests on custom routes) appeared without thebolt-appprefix.Behaviour change for the no-
loggercase: the default receiver now shares the sameLoggerinstance asapp.logger, so a downstreamapp.logger.setLevel(...)after construction will affect receiver-side logging too. This is consistent with the existing behaviour that already mutatesthis.logger's level via thelogLevelconstructor option. Apps that supplied their ownloggerare unaffected; apps that relied on the receiver's logger being independent ofapp.loggerwill need to pass a separateloggerinto the receiver explicitly.e1c21d7: FixAwsLambdaReceiver.toHandler()so Bolt apps on the AWS Lambda Node.js 24+ runtime no longer fail at startup withRuntime.CallbackHandlerDeprecated. The returned handler is now a 2-arg promise-based function; the unused trailingcallbackparameter has been removed from theAwsHandlertype. The legacyAwsCallbackexport is retained and marked@deprecated.f2de079: Addcontext_team_idandcontext_enterprise_idas optional fields on theEnvelopedEventtype. Slack's Events API delivers these on the envelope for Slack Connect channels and Enterprise Grid org-wide apps, whereteam_idmay 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-erroror unsafe casts to route by the correct workspace.Configuration
📅 Schedule: (in timezone UTC)
* 0-4 * * 7)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by self-hosted Renovate.