Add Slack failure notification to baml-language-release workflow

[sxlijin]

Issue Reference

N/A - Direct request from Slack

Changes

Added a Slack notification job to the release-baml-language.yml workflow that:

• Runs only when a non-dry-run release fails (checks publish-pkg-boundaryml-com job failure)
• Uses the boundary-tools-dev GitHub environment
• Posts a failure notification to Slack channel #general
• Uses SLACK_BOUNDARY_BOT_TOKEN from the environment secrets
• Includes version, channel, and workflow run link in the failure notification

The notification job is configured to run only when:

• dry_run == false
• source_branch == 'canary'
• publish-pkg-boundaryml-com.result == 'failure'

Testing

• Manual testing performed
• Tested in boundary-tools-dev environment

The workflow change can be tested by:

1. Triggering a release workflow run that fails
2. Verifying the Slack failure notification is posted to #general

PR Checklist

• I have read and followed the contributing guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• My changes generate no new warnings

Additional Notes

The Slack notification will only be sent for failed non-dry-run releases from the canary branch. The job requires the following environment variables to be configured in the boundary-tools-dev environment:

• SLACK_BOUNDARY_BOT_TOKEN (required for authentication)

The notification uses #general as the channel name, which the Slack API will resolve to the appropriate channel ID.

Slack Thread

  

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
beps	Ready	Preview, Comment	Jul 22, 2026 5:35pm
promptfiddle	Ready	Preview, Comment	Jul 22, 2026 5:35pm
promptfiddle2	Ready	Preview, Comment	Jul 22, 2026 5:35pm

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: beee00e3-76d8-4cdc-a249-a43cab7f4634

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/add-slack-notification-1a46

---

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.}

[github-actions]

⏭️ Performance benchmarks were skipped

Perf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to canary/main.

To run them on this PR, do any of the following, then push a commit (or re-run CI):

• Add RUN_CODSPEED=1 to the PR description, or
• Include run-perf or /perf in the PR title or any commit message.

[github-actions]

Binary size checks passed

✅ 7 passed

	Artifact	Platform	File	Gzip	Gated on	Baseline	Delta	Status
✅	baml-cli	Linux	🔒 25.6 MB	10.8 MB	file	25.3 MB	+275.0 KB (+1.1%)	OK
✅	packed-program	Linux	🔒 17.2 MB	7.1 MB	file	17.0 MB	+153.1 KB (+0.9%)	OK
✅	baml-cli	macOS	🔒 19.8 MB	9.4 MB	file	19.6 MB	+231.5 KB (+1.2%)	OK
✅	packed-program	macOS	🔒 13.4 MB	6.2 MB	file	13.2 MB	+198.3 KB (+1.5%)	OK
✅	baml-cli	Windows	🔒 21.3 MB	9.7 MB	file	21.1 MB	+230.9 KB (+1.1%)	OK
✅	packed-program	Windows	🔒 14.3 MB	6.3 MB	file	14.2 MB	+150.5 KB (+1.1%)	OK
✅	bridge_wasm	WASM	16.3 MB	🔒 4.4 MB	gzip	4.4 MB	+19.2 KB (+0.4%)	OK

🔒 = the size this artifact is GATED on (ceiling + delta). Binaries gate on file size (installed binary); WASM gates on gzip (download size). The other size is shown for information only.

---

Generated by cargo size-gate · workflow run