Skip to content

Releases: slackapi/bolt-js

@slack/bolt@2.2.0

21 Jul 00:08
Compare
Choose a tag to compare

@slack/bolt@2.1.1-workflowStepsBeta.1

20 Jul 23:54
Compare
Choose a tag to compare
Pre-release

This release is for the Workflow Steps from Apps beta. 🎉

Install via npm install @slack/bolt@feat-workflow-steps

@slack/bolt@1.8.1

06 Jul 19:54
Compare
Choose a tag to compare
  • 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

23 May 00:49
Compare
Choose a tag to compare
  • Fixed a bug with custom ExpressReceivers not working properly with the new OAuth changes. (#503) - Thanks @stevengill & @marks

@slack/bolt@2.1.0

22 May 19:28
Compare
Choose a tag to compare

@slack/bolt@2.0.1

11 Apr 00:09
Compare
Choose a tag to compare
  • 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

30 Mar 19:39
Compare
Choose a tag to compare

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 the action() 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 to App[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

18 Mar 15:06
Compare
Choose a tag to compare

@slack/bolt@1.7.0

06 Mar 01:42
Compare
Choose a tag to compare

@slack/bolt@1.6.0

05 Feb 01:38
Compare
Choose a tag to compare
  • Added logger and client to the list of arguments sent through to listeners (such as event, message, etc.). This makes it easier for listeners to make calls to Web 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 of 500 for signature verification failures (#324, #362) - thanks @seratch
  • Fixed ack in ExpressReceiver 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