Skip to content

ci: announce CLI releases in Slack - #20

Merged
hassan-bazzi merged 1 commit into
mainfrom
ci/slack-release-alerts
Oct 4, 2026
Merged

hassan-bazzi merged 1 commit into
mainfrom
ci/slack-release-alerts

Conversation

@hassan-bazzi

@hassan-bazzi hassan-bazzi commented Oct 4, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • notify Slack #alerts after successful CLI releases from either release workflow
  • use the channel-bound incoming webhook already used by production alerts
  • validate release tags and build the Slack payload with jq to avoid markup injection
  • add retries and fail the workflow if the release notification cannot be delivered

Verification

  • bash -n scripts/notify-slack-release.sh scripts/release-version.sh
  • local mock webhook test validates the v2.2.2 payload and release URL
  • invalid-tag test fails closed
  • git diff --check

Release plan

After merge, dispatch Release (Manual) with a patch bump to publish v2.2.2 and verify the message appears in #alerts.

Summary by CodeRabbit

  • New Features
    • Release events now trigger Slack notifications containing the release tag and a link to the release.
    • Notifications are sent for releases initiated through either supported release workflow.

@coderabbitai

coderabbitai Bot commented Oct 4, 2026

Copy link
Copy Markdown

Review in Change Stack →

Navigate logical layers of code changes, visualize relationships, and explore their blast radius.

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 7f39a7a4-273c-4f1e-8fe3-e89e8359741f
📥 Commits

Reviewing files that changed from the base of the PR and between 03de330 and d07997d.

📒 Files selected for processing (3)
  • .github/workflows/release-dispatch.yml
  • .github/workflows/release.yml
  • scripts/notify-slack-release.sh
 _____________________
< 🧯 Bug extinguished. >
 ---------------------
  \
   \   (\__/)
       (•ㅅ•)
       /   づ
✨ Finishing Touches
📝 Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@hassan-bazzi

Copy link
Copy Markdown
Contributor Author

Required review summary

Codex: PASS — no actionable defects.

Security review

Verdict: PASS

  • The webhook remains in GitHub Actions secrets and is never printed or committed.
  • Tags are restricted to vMAJOR.MINOR.PATCH before use.
  • Slack text uses plain_text; the payload is generated with jq, so untrusted markup cannot create mentions or injected links.
  • The release URL is repository-controlled.

Performance review

Verdict: PASS

  • Adds one small webhook POST after a successful release.
  • Retries are bounded to three attempts and do not affect CLI runtime behavior.

Correctness review

Verdict: PASS

  • Both supported release paths call the same notifier after GoReleaser succeeds.
  • The manual workflow captures the exact newly-created tag through GITHUB_OUTPUT.
  • Mock webhook verification confirmed the v2.2.2 payload and release URL; invalid tags fail closed.
  • bash -n, ShellCheck, and git diff --check pass.

No waivers or blockers identified.

@hassan-bazzi
hassan-bazzi merged commit db40b55 into main Oct 4, 2026
1 of 2 checks passed
@hassan-bazzi
hassan-bazzi deleted the ci/slack-release-alerts branch October 4, 2026 19:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant