Releases: slackapi/bolt-js
Releases · slackapi/bolt-js
@slack/bolt@2.2.0
- Made updates for English and Japanese docs (#417, #513, #515, #518, #522, #527, #535, #547) - Thanks, @greggTime, @stevengill, and @seratch!
- Added
calls_rejected
event (#505, #506) - Thanks, @stevengill! - Added new middleware to filter out
app_mention
events (#499) - Thanks, @hashedhyphen! - Added text as an optional property for RespondArguments (#512) - Thanks, @aoberoi!
- Added
userScopes
toAppOptions
(#540) - Thanks, @joshmcgrath08! - Added new interface types for
ReactionAddedEvent
(#537) - Thanks, @dbmikus!
@slack/bolt@2.1.1-workflowStepsBeta.1
This release is for the Workflow Steps from Apps beta. 🎉
- Added Workflow Steps support (#546) - Thanks, @selfcontained!
Install via npm install @slack/bolt@feat-workflow-steps
@slack/bolt@1.8.1
- added runtime deprecation notice for @slack/bolt 1.x (#533). Please upgrade to the latest version of bolt-js! - Thanks @stevengill
@slack/bolt@2.1.1
- Fixed a bug with custom
ExpressReceivers
not working properly with the new OAuth changes. (#503) - Thanks @stevengill & @marks
@slack/bolt@2.1.0
- Integrated the Slack OAuth package into Bolt-js. Checkout the Bolt-js docs to learn more! (#479) - Thanks @stevengill
- changed deprecated usage of
res.send
tores.status(500).send()
(#487) - Thanks @dburandt - updates to docs (#477) - Thanks @shaydewael
- Added type aliases for
RadioButton
andCheckbox
(#471) - Thanks @yoichiro
@slack/bolt@2.0.1
- Fixes bug where
processBeforeResponse
option did not ensure processing was complete before HTTP response was sent (#462) - thanks @aoberoi - Adds the new Bolt for JS brand assets in the documentation site and README ($468) - thanks @shaydewael
- Adds Bolt for JS v2 Migration Guide in Japanese (#457) - thanks @seratch
- Corrects badly formatted string in the documentation example code (#460, #461) - thanks @takayukioda
@slack/bolt@2.0.0
Thanks for checking out the 2.0.0
release of Bolt for JavaScript! Firstly, a huge thank you to all of the folks who contributed to this release. A special shoutout to community contributor @barlock for the massive contributions he contributed!
Make sure to read the migrating to 2.0.0
guide to learn what changes are needed to upgrade your existing Bolt for JavaScript apps.
- Chaining middleware via promises. This allows the ability to test listeners and middlewares without artificial delays. This change also allows Bolt to run on Functions-as-a-Service platforms (such as AWS Lambda) by allowing the
processBeforeResponse
option to be used. (#353, #380, #381, #439, #440, #444) - Thanks @barlock, @aoberoi, @stevengill and @seratch - Message shortcuts (previously referred to as message actions) now use the
shortcut()
method instead of theaction()
method. (#428) - Thanks @stevengill - Fix
View
type missing optional id from response (#436, #437) - Thanks @seratch - Added Migration Guide for
@slack/bolt@2.0.0
(#442, #445, #449) - Thanks @stevengill - Added
processBeforeResponse
toApp[Options]
to improve Bolt support for Function-as-a-Service platforms (like AWS Lambda) (#444) - Thanks @stevengill - Set minimum TypeScript version to 3.7.0 (#447, #452) - Thanks @aoberoi and @stevengill
@slack/bolt@1.8.0
- Added Global Shortcuts support with the new
.shortcut
method (#427, #430) - thanks @stevengill & @shaydewael - Replaced
bolt
withbolt for javascript
in our documentation (#425) - thanks @shaydewael - Fix invalid fields in
MultiUsersSelectAction
(#422, #423) - thanks @seratch
@slack/bolt@1.7.0
@slack/bolt@1.6.0
- Added
logger
andclient
to the list of arguments sent through to listeners (such as event, message, etc.). This makes it easier for listeners to make calls toWeb API
methods while keeping the client rate-limit and queue-aware. (#359, #168, #354) - thanks @seratch - Added support for the
invite_requested
event type (#382, #387) thanks @seratch - Update Bolt getting started guide for Granular Bot Permissions (#373, #378) - thanks @shaydewael
- Respond with
401
status code instead of500
for signature verification failures (#324, #362) - thanks @seratch - Fixed
ack
inExpressReceiver
firing twice. (#327 #370) - thanks @jarrodldavis ExpressReceiver's
RespondFn
implementation now accepts a string (#377, #379) - thanks @seratch- Added more unit tests for built-in middleware and
ExpressReceiver
(#357) - thanks @seratch - Minor docs updates (#352, #356, #363, #374) - thanks @koh110, @seratch, @byrondover