ci: alert Slack on release failure

[ugnsma]

Adds a notify-failure job to build-release.yaml that posts a Slack alert when the release pipeline fails.

[coderabbitai]

Warning

Review limit reached

@ugnsma, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 4f37bcc4-940c-4e32-9d2d-cb3db714c15a

📥 Commits

Reviewing files that changed from the base of the PR and between cfbf66d and 3fdccbb.

📒 Files selected for processing (1)

• .github/workflows/build-release.yaml

📝 Walkthrough

Walkthrough

The release workflow adds a notify-failure job that runs after build and release, detects failures, and sends Slack notifications containing repository, commit, and failed-run information.

Changes

Failure notification

Layer / File(s)	Summary
Slack failure notification job .github/workflows/build-release.yaml	Adds a conditional job dependent on build and release, using the Slack GitHub Action and webhook secret to post failure context and a link to the failed run.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: aurimasbutkus

Sequence Diagram(s)

sequenceDiagram
  participant Build as build job
  participant Release as release job
  participant Notify as notify-failure job
  participant Slack as Slack webhook
  Build-->>Notify: job result
  Release-->>Notify: job result
  Notify->>Slack: post failure payload

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: sending a Slack alert when release-related jobs fail.
Description check	✅ Passed	The description matches the workflow change and explains the failure notification behavior and secret requirement.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/release-failure-slack-alert

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/build-release.yaml:
- Line 63: Replace the mutable v2.1.0 tag in the Slack action step with the full
immutable commit SHA corresponding to slackapi/slack-github-action v2.1.0,
preserving the release notification configuration and webhook usage.
- Line 75: Update the Slack payload’s commit reference near the notification
template to avoid inserting github.event.head_commit.message directly; use
github.sha or a separately generated, escaped and length-limited JSON-safe value
instead, while preserving the existing commit context in the message.
- Around line 62-66: Update the “Notify Slack on release failure” step using
slackapi/slack-github-action@v2.1.0 to enable its error-failing behavior by
setting the action’s errors input to true, so non-200 Slack responses fail the
notification job.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 0219e7d9-9cdb-4282-8a3b-12de19362abb

📥 Commits

Reviewing files that changed from the base of the PR and between 676a30b and cfbf66d.

📒 Files selected for processing (1)

• .github/workflows/build-release.yaml