feat: add automated Slack release notifications

Add GitHub Actions workflow that posts to Slack when a release is published:
- Posts to #topic-cf-gitops-runtime with release version and link
- Cross-posts to #team-support-announcements
- Includes workflow_dispatch trigger for manual testing

Update release guide:
- Document that announcements are now automated
- Add troubleshooting section for Slack notifications
- Add Slack integration setup instructions in Reference section

Author: dmaizel

.github/workflows/release-notification.yaml

@@ -0,0 +1,65 @@
+# ABOUTME: GitHub Actions workflow that posts Slack notifications when a release is published.
+# ABOUTME: Notifies #topic-cf-gitops-runtime and cross-posts to #team-support-announcements.
+
+name: Release Notification
+
+on:
+  release:
+    types: [published]
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: 'Release tag to simulate (e.g., 0.27.0)'
+        required: true
+  # TODO: Remove after first successful test
+  push:
+    branches:
+      - docs/update-release-guide-validation-announcements
+
+jobs:
+  notify-slack:
+    # Skip on push trigger - it's only used to register the workflow in Actions tab
+    if: github.event_name != 'push'
+    runs-on: ubuntu-latest
+    env:
+      RELEASE_TAG: ${{ github.event.release.tag_name || inputs.tag }}
+      RELEASE_URL: ${{ github.event.release.html_url || format('https://github.com/{0}/releases/tag/{1}', github.repository, inputs.tag) }}
+    steps:
+      - name: Notify #topic-cf-gitops-runtime
+        uses: slackapi/[email protected]
+        with:
+          method: chat.postMessage
+          token: ${{ secrets.SLACK_BOT_TOKEN }}
+          payload: |
+            channel: ${{ vars.SLACK_CHANNEL_GITOPS_RUNTIME }}
+            text: "GitOps Runtime ${{ env.RELEASE_TAG }} has been released"
+            blocks:
+              - type: header
+                text:
+                  type: plain_text
+                  text: "🚀 GitOps Runtime Release"
+              - type: section
+                fields:
+                  - type: mrkdwn
+                    text: "*Version:*\n${{ env.RELEASE_TAG }}"
+              - type: actions
+                elements:
+                  - type: button
+                    text:
+                      type: plain_text
+                      text: "View Release Notes"
+                    url: ${{ env.RELEASE_URL }}
+
+      - name: Cross-post to #team-support-announcements
+        uses: slackapi/[email protected]
+        with:
+          method: chat.postMessage
+          token: ${{ secrets.SLACK_BOT_TOKEN }}
+          payload: |
+            channel: ${{ vars.SLACK_CHANNEL_SUPPORT_ANNOUNCEMENTS }}
+            text: "GitOps Runtime ${{ env.RELEASE_TAG }} has been released"
+            blocks:
+              - type: section
+                text:
+                  type: mrkdwn
+                  text: "*GitOps Runtime ${{ env.RELEASE_TAG }}* has been released.\n\n<${{ env.RELEASE_URL }}|View release notes>"

docs/RELEASE_GUIDE.md

@@ -208,27 +208,13 @@ Check the release:
 gh release view 0.27.0 --repo codefresh-io/gitops-runtime-helm
 ```
 
-### Step 5: Announce the Release
+### Step 5: Announcement (Automated)
 
-After the release is published, announce it to the team:
+When a release is published, a GitHub Actions workflow automatically posts announcements to:
+- `#topic-cf-gitops-runtime` - Primary announcement with release version and link
+- `#team-support-announcements` - Cross-post for the support team
 
-1. **Post in `#topic-cf-gitops-runtime`**:
-   - Introduce the release with a brief summary of key changes
-   - Include a link to the GitHub release notes
-
-   Example:
-   ```
-   :rocket: GitOps Runtime v0.27.0 has been released!
-
-   Highlights:
-   - [Key feature or fix 1]
-   - [Key feature or fix 2]
-
-   Release notes: https://github.com/codefresh-io/gitops-runtime-helm/releases/tag/0.27.0
-   ```
-
-2. **Cross-post to `#team-support-announcements`**:
-   - Share the same announcement so the support team is aware of the new release
+No manual action required. If notifications don't appear, see [Troubleshooting: Slack Notifications Not Sent](#slack-notifications-not-sent).
 
 ---
 
@@ -432,6 +418,25 @@ git push --force-with-lease
    gh release edit 0.27.0 --repo codefresh-io/gitops-runtime-helm --draft=false
    ```
 
+### Slack Notifications Not Sent
+
+**Symptom**: Release published but no Slack notifications appeared
+
+**Check**:
+1. Verify the `release-notification` workflow ran:
+   - Go to Actions tab → "Release Notification" workflow
+   - Check for failed runs
+2. If workflow failed, check for:
+   - Missing `SLACK_BOT_TOKEN` secret
+   - Missing `SLACK_CHANNEL_GITOPS_RUNTIME` or `SLACK_CHANNEL_SUPPORT_ANNOUNCEMENTS` variables
+   - Bot not invited to the channels
+3. Manual fallback - post manually to Slack:
+   ```
+   🚀 GitOps Runtime vX.Y.Z has been released!
+
+   Release notes: https://github.com/codefresh-io/gitops-runtime-helm/releases/tag/X.Y.Z
+   ```
+
 ---
 
 ## Reference
@@ -472,6 +477,22 @@ git push --force-with-lease
 |------|---------|
 | `charts/gitops-runtime/Chart.yaml` | Version, changelog annotations |
 | `charts/gitops-runtime/values.yaml` | Component versions, defaults |
+| `.github/workflows/release-notification.yaml` | Slack release announcements |
+
+### Slack Integration Setup
+
+The release notification workflow requires a Slack App with bot token. One-time setup:
+
+1. **Create Slack App** at https://api.slack.com/apps
+2. **Add OAuth Scope**: Go to "OAuth & Permissions" → add `chat:write`
+3. **Install to Workspace**: Click "Install to Workspace" and authorize
+4. **Copy Bot Token**: Copy the "Bot User OAuth Token" (starts with `xoxb-`)
+5. **Get Channel IDs**: Right-click each channel → "View channel details" → copy the Channel ID
+6. **Invite Bot**: In each Slack channel, run `/invite @YourBotName`
+7. **Add to GitHub**:
+   - Secret: `SLACK_BOT_TOKEN` → the bot token from step 4
+   - Variable: `SLACK_CHANNEL_GITOPS_RUNTIME` → channel ID for #topic-cf-gitops-runtime
+   - Variable: `SLACK_CHANNEL_SUPPORT_ANNOUNCEMENTS` → channel ID for #team-support-announcements
 
 ---