From e67b52a6f410b08d19c1c3c496f5edcb024b8a5e Mon Sep 17 00:00:00 2001 From: Joe Li Date: Wed, 6 May 2026 16:30:15 -0700 Subject: [PATCH] docs(updating): rewrite slack v1 deprecation note in conventional one-liner style Replaces the multi-section paragraph form with the single-bullet, PR-link-prefixed style used by the historical entries in this file (see the original Slack v2 deprecation in 4.1.0 / #29264). Same information, less ceremony. Co-Authored-By: Claude Opus 4.7 (1M context) --- UPDATING.md | 10 +--------- 1 file changed, 1 insertion(+), 9 deletions(-) diff --git a/UPDATING.md b/UPDATING.md index 5241c54ddb9..abfa11e186f 100644 --- a/UPDATING.md +++ b/UPDATING.md @@ -24,15 +24,7 @@ assists people when migrating to a new version. ## Next -### Slack v1 deprecated; `ALERT_REPORT_SLACK_V2` defaults to `True` - -The legacy Slack integration for Alerts and Reports (`Slack` recipient type, `files.upload` API) is deprecated and will be removed in the next major release. The `ALERT_REPORT_SLACK_V2` feature flag now defaults to `True`. - -**Why this is changing:** Slack retired the `files.upload` endpoint in 2025, so v1 sends that include screenshots, CSVs, or PDFs already fail at the API level. Only text-only `chat_postMessage` sends still succeed via the legacy path. The v2 integration uses `files_upload_v2` and stores stable channel IDs instead of mutable channel names. - -**Operator action required:** Grant your Slack bot the `channels:read` scope (and `groups:read` if you use private channels). With that scope in place, existing `Slack` recipients are auto-upgraded to `SlackV2` on their next successful send — channel names are resolved to channel IDs and the recipient row is rewritten in place. Recipients whose channels can't be resolved will continue to send via the v1 `chat_postMessage` path for text-only alerts until v1 is removed. - -**If you previously set `ALERT_REPORT_SLACK_V2: False` explicitly:** you'll see a one-shot `DeprecationWarning` and a `logger.warning` describing the action above. To suppress, remove the override or grant the scope and let the auto-upgrade run. +- [39914](https://github.com/apache/superset/pull/39914) `ALERT_REPORT_SLACK_V2` now defaults to `True` and the legacy Slack v1 integration (`Slack` recipient type, `files.upload` API) is deprecated for removal in the next major. Slack retired `files.upload` in 2025, so v1 file-bearing sends already fail at the API level — only text-only `chat_postMessage` still works via the legacy path. Grant your Slack bot the `channels:read` scope (and `groups:read` for private channels) so existing `Slack` recipients can be auto-upgraded to `SlackV2` on next send. Operators who explicitly override the flag to `False` will see a one-shot `DeprecationWarning` plus a `logger.warning`; remove the override or grant the scope to clear it. ### Granular Export Controls