Closed arunsathiya closed 10 months ago
Good question! I lean towards agreeing with you. Will raise it with the team.
Hello @arunsathiya , thank you for the flag. To your question:
@arunsathiya I'll look at updating my repo later today. Thanks for your interest in the platform!
On Mon, Oct 30, 2023, 10:40 AM Cheng Chen @.***> wrote:
Hello @arunsathiya https://github.com/arunsathiya , thank you for the flag. To your question:
- The legacy version of Slack CLI requires auth token to perform upgrade
- We do not require auth token to upgrade Slack CLI anymore in the newer versions
- To unblock you, please go to https://api.slack.com/automation/quickstart to reinstall Slack CLI based on your platform.
— Reply to this email directly, view it on GitHub https://github.com/slackapi/deno-slack-sdk/issues/236#issuecomment-1785362715, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABMW5QAI5WUEQIRUL37M6LYB635BAVCNFSM6AAAAAA6VDCG4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBVGM3DENZRGU . You are receiving this because you were mentioned.Message ID: @.***>
Ah I failed to see that @arunsathiya was upgrading from v1.8 of the CLI - indeed a very old version.
Since slack upgrade
no longer relies on a valid token, I will close this issue.
Awesome, that explains it! Thanks everyone.
(I'd file this issue on the Slack CLI project, but it seems to be a private repository)
Question
It seems that
slack upgrade
requires a valid auth token. Is that expected? I'd imagine that upgrading the CLI shouldn't require a valid auth token, similar to downloading the latest version manually.Context
Ran into this error when setting up @hirefrank's GitPod template:
Environment