Releases: slackapi/node-slack-sdk
Releases · slackapi/node-slack-sdk
@slack/client v3.6.0
- Adds support for Incoming Webhooks
- Fixes a bug around User IDs
@slack/client v3.5.4
- Fixes a bug whereby events with fields not recognized cause a crash. Wow.
- Updated some logic around what user ids look like.
@slack/client v3.5.3
- Fixes a bug in the
package.json
published by 3.5.2.
@slack/client v3.5.2
- Updating the links in
package.json
so that you don't need SSL credentials to pull down the github repo.
@slack/client v3.5.1
- Updates
lodash
from^3.10.1
to^4.13.1
. And means it. - Minor tweaks to existing documentation and example code to make them consistent with each other. Because hobgoblins are friendly and love you.
@slack/client v3.5.0
- Adds the team.billableInfo endpoint to the team facet
- Adds the bots.info endpoint and creates the
bots
facet - Removes the
user
optional argument from the stars.list method
@slack/client v3.4.0
- Adds the chat.meMessage endpoint to the chat facet
@slack/client v3.3.0
- Creates a memory data store by default if an undefined, but not false|null value is passed for
opts.dataStore
- Aliases the retry policies to be human readable
@slack/client v3.2.1
- Updates the RTM client to emit an UNABLE_TO_RTM_START event when all reconnection attempts are exhausted, rather than throwing an error
- Suppresses some spurious log lines when tests are run
@slack/client v3.2.0
- Updates the
_makeAPICall
method to make the optional API args param optional to pass in, so the third param to this function can be either an opts object or a cb. This is to allow us to add optional arguments to API methods without it being a breaking change. - Fixes the
retry-after
header name and adds a numeric fallback if the retry-after value can't be parsed, thanks @foiseworth! - Adds new API methods to various facets
- Adds optional arguments to:
files.comments.add
: adds achannel
param, for the channel id of the location to associate with the new commentchat.delete
: adds a booleanas_user
param, to support deleting a message as the authed user