From 84ac9eb5f125a074fdcf2d10929be98b1a8bd159 Mon Sep 17 00:00:00 2001 From: Eden Zimbelman Date: Tue, 30 Jun 2026 15:54:45 -0700 Subject: [PATCH] docs: fix unclosed info admonition in authorizing-the-slack-cli The `:::info` block about `--skip-update` / `SLACK_SKIP_UPDATE` being ignored by `slack upgrade` was missing the closing `]` on its title. The unclosed title bracket caused the MDX renderer to mangle later content on the page, surfacing a stray `authorize-cli}` in the preview. Co-Authored-By: Claude --- docs/guides/authorizing-the-slack-cli.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/authorizing-the-slack-cli.md b/docs/guides/authorizing-the-slack-cli.md index 0490b62b..aa412322 100644 --- a/docs/guides/authorizing-the-slack-cli.md +++ b/docs/guides/authorizing-the-slack-cli.md @@ -65,7 +65,7 @@ Update notifications can be disabled using a command-line flag or an environment When the CLI runs in a non-interactive environment, such as inside a CI/CD pipeline or when the output is piped, the update check runs without the auto-update confirmation prompt. The notification text may still appear in command output, however. You can suppress the check entirely with the `--skip-update` flag or `SLACK_SKIP_UPDATE` environment variable to keep the automation output clean. -:::info[The `--skip-update` flag and the `SLACK_SKIP_UPDATE` environment variable are intentionally ignored when running the `slack upgrade` command directly, since that command's purpose is to check for updates. +:::info[The `--skip-update` flag and the `SLACK_SKIP_UPDATE` environment variable are intentionally ignored when running the `slack upgrade` command directly, since that command's purpose is to check for updates.] ::: ## CI/CD authorization {#ci-cd}