feat(ci): add Slack failure notifications

[wyattjoh]

Summary

• Add scripts/slack.ts that posts block-kit formatted failure messages to a Slack incoming webhook
• Extract a reusable notify-failure.yml workflow to keep notification steps DRY across CI, stable release, and canary release pipelines

Requirements

Requires a SLACK_WEBHOOK_URL repository secret.

Test plan

• Verify notify-failure.yml is triggered when a CI job fails
• Verify Slack message format renders correctly
• Confirm no regressions in existing CI or release workflows

[wyattjoh]

Stack: slack-notifications

• feat(ci): add Slack failure notifications #151 👈 this PR
  • refactor(ci): extract reusable CI checks and setup-bun composite action #152

Part of a stacked PR chain. Do not merge manually.

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

Added a reusable GitHub Actions workflow .github/workflows/notify-failure.yml callable via workflow_call that accepts a required workflow-name input and a required SLACK_WEBHOOK_URL secret, checks out the repo, sets up Bun, installs dependencies, and runs bun scripts/slack.ts --status failure. Updated .github/workflows/release.yml to add notify-stable-failure and notify-canary-failure jobs that run the reusable workflow when specified upstream jobs include failures. Added scripts/slack.ts, a Bun script that requires --status, reads WORKFLOW_NAME and SLACK_WEBHOOK_URL from the environment, composes a Slack Block Kit payload with workflow and run metadata, and POSTs it to the webhook with error handling.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: adding Slack failure notifications to CI workflows.
Description check	✅ Passed	The description is clearly related to the changeset, detailing the specific changes made and test requirements.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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

[changeset-bot]

⚠️ No Changeset found

Latest commit: 427678f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Railly]

Looked through it, LGTM. Clean split between Slack for release pipeline failures and PR comments for snapshots. Nothing to flag, approve from me.