@slack/[email protected]

• 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

@slack/[email protected]

• Added support for radio button types in App Home (#299) - Thanks @shaydewael
• Some nice docs fixes (#318) (#319) - Thanks @yamashush, @shaydewael
• Updated the dependency version of @slack/web-api to include support for modals (#322) and then again for granular bot permissions (#335) - Thanks @PerStirpes, @seratch and @stevengill
• Added type as a valid constraint for app actions. (#326) - Thanks @selfcontained
• Fixed some linting issues (#339) - Thanks @tteltrab
• Removed users.info call from SingleTeamAuthorization since auth.test includes the bot_id. This allows developers to reduce scope by creating Bolt apps without a users:read scope. (#347) - Thanks @pichsenmeister
• For our Typescript users, we made the channel field in block_actions payload optional (#343), added support for multi-select actions (#344), and improved type resolution for action method (#349) - Thanks @seratch and @stevengill

@slack/[email protected]

• Adds updated types for the app_home_opened event. The event now contains a tab property, which can be set to "home" or "messages". The event might also contain a view property. These changes are in support of App Home Home Tabs. (#292) thanks @seratch!

@slack/[email protected]

• Adds a much-anticipated enhancement to fire member_joined_channel and member_left_channel events for your own bot (#236) - thanks @TK95 🎉
• Adds the ability to pass in WebClient options into the constructor (#228 and #278) - thanks @koh110 and @aoberoi ⚙️
• Adds Japanese 🇯🇵documentation for Block Kit in modals (#268) - thanks @seratch
• Fixes some typos and mistranslations in the Japanese documentation (#279) - thanks @grgr-dkrk
• Adds view_closed for Block Kit in modals (uses the same view() method) (#276) - thanks @shanedewael
• Removes redundant types for please-upgrade-node (#253) - thanks @43081j
• Adds tests to for the incoming event handler (#269) - thanks @seratch
• Updates logger + documentation to use getLevel() (#270 and #285)- thanks @shanedewael
• Fixes a bug with custom receiver being overwritten when signingSecret was passed into constructor (#271) - thanks @shanedewael
• Adds a maintainer guide (#272) - thanks @shanedewael
• Fixes a JA documentation inconsistency (#273) - thanks @ikenami

@slack/[email protected]

• Adds new view() method that allows you to listen to view_submission events - thanks @shanedewael
• Adds new types and documentation for using Block Kit in modals - thanks @shanedewael
• Fix the Web API documentation - thanks @PerStirpes

@slack/[email protected]

• Adds support for rawBody in signature verification which enables serverless (GCP) deployments of Bolt (fixes #192) - thanks @seratch
• Fixes message action support (fixes #201) - thanks @shanedewael
• Adds improvements to App.spec.js - thanks @seratch

@slack/[email protected]

• Bolt will now fail with an error on initialization when it is started using an incompatible Node version (#174) - thanks @aoberoi
• Bug fix: subtype() built-in middleware used an inverted logical condition (#180) - thanks @shanedewael
• Bug fix: Errors from calling say() utility were not handled using the global error handler (#183) - thanks @sethlu and @aoberoi
• Bug fix: The conversationContext() default built-in middleware did not allow events without a channel context to flow through handlers (#185) - thanks @aoberoi
• Bug fix: The matchMessage() and directMention() built-in middleware would fail to process messages without text, such as Block Kit composed messages (#182) - thanks @aoberoi
• Tons of improvements to the Getting Started guide, and other docs (#170, #171, #177, #178, #181, #186, #188, #193, #194) - thanks @shanedewael, @0xflotus, and @seratch.

@slack/[email protected]

• Fix block action detection and removes StringIndexed from action body types (#166) - thanks @aoberoi
• Fail early for unknown constraints (#167) - thanks @aoberoi

Introducing Bolt - v1.0.0

Bolt is a framework for building Slack apps, fast.

Get started to build your team's next productivity enhancer, social sidekick, or just have some fun with memes. Bolt makes it a cinch listen in on the Events API, send composed messages, respond to interactions in those messages, and more.

Get more details in the full documentation.

Where is Slapp?

Bolt wouldn't be possible without all the amazing work from Slapp contributors and community - it evolved from the Slapp codebase. Slapp will continue to be supported on the v3 branch but we'd really like existing Slapp users to give Bolt a try. We've been mindful to make sure Slapp apps will translate over without too much pain, and will be publishing a migration guide in the future.

@slack/[email protected]

@slack/[email protected]