[2kai2kai2]

Due to crates.io trusted publishing security policy, workflow_run is rejected. We now explicitly dispatch from the CI run.

Summary by CodeRabbit

• New Features

  • Canary builds now automatically trigger the language release workflow after required CI checks pass.
  • Releases can be dispatched with a specific source commit and automatic channel selection.
  • Nightly releases are queued using the exact commit published to the canary channel.

• Bug Fixes

  • Improved release reliability by preventing releases from starting after failed or cancelled CI runs.

[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 7:18pm
promptfiddle	Ready	Preview, Comment	Jul 22, 2026 7:18pm
promptfiddle2	Ready	Preview, Comment	Jul 22, 2026 7:18pm

[coderabbitai]

📝 Walkthrough

Walkthrough

The CI workflow now dispatches the release workflow after successful canary pushes. The release workflow is dispatch-only, accepts an optional source commit, maps auto to nightly, and propagates the planned commit to nightly releases.

Changes

Canary release automation

Layer / File(s)	Summary
Canary CI release dispatch .github/workflows/ci.yaml	Adds a gated dispatch-release job that launches the release workflow with channel=auto, dry_run=false, and the current commit SHA.
Release planning and source propagation .github/workflows/release-baml-language.yml	Converts release execution to workflow_dispatch, accepts source_sha, uses it for checkout, maps auto to nightly, and forwards it to nightly dispatches.

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

Sequence Diagram(s)

sequenceDiagram
  participant CI as CI workflow
  participant Release as Release workflow
  participant Plan as Plan release
  participant Nightly as Nightly workflow
  CI->>Release: Dispatch after successful canary CI
  Release->>Plan: Pass channel and source_sha
  Plan->>Plan: Resolve auto to nightly and checkout source
  Plan->>Nightly: Dispatch pinned source_sha

Loading

Possibly related PRs

• BoundaryML/baml#3674: Updates release planning and downstream nightly publishing paths.
• BoundaryML/baml#3694: Adds SDK publishing jobs that consume release plan inputs.
• BoundaryML/baml#4037: Adds build and publish steps relying on release source and plan inputs.

Suggested reviewers: antoniosarosi, hellovai, codeshaunted

Poem

I’m a rabbit in the canary lane,
Dispatching releases through sun and rain.
A pinned SHA hops neatly along,
While nightly workflows sing their song.
CI thumps its paws: “All green!” 🐇

🚥 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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly reflects the main change: switching the release workflow from workflow_run to dispatch.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch kai/rust-bridge-publishing

---

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