Closed castrojo closed 3 years ago
Here is the deprecation information https://api.slack.com/changelog/2020-01-deprecating-antecedents-to-the-conversations-api
@castrojo @mrbobbytables -- Can I take this up? :)
Of course you can @palnabarun :)
cc @pymander He was interested in helping too :)
It looks like a pretty simple change, and I am happy to let @palnabarun take it.
@pymander @mrbobbytables -- I took a dig at it last weekend. The change needed is indeed simple.
I am wondering if there is a way I can test the change without setting up the whole bot in a new Slack workspace like described in docs/app-creation.md. What do you think?
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen
.
Mark the issue as fresh with /remove-lifecycle rotten
.
Send feedback to sig-contributor-experience at kubernetes/community. /close
@fejta-bot: Closing this issue.
From Katharine in slack: Apparently the welcomer bot uses a deprecated API, nothing else does , looks like it’s just this line that needs changing:
https://github.com/kubernetes-sigs/slack-infra/blob/master/slack-welcomer/handler.go#L133