[rossirpaulo]

Summary

• run the crates.io publisher under the existing boundary-tools-prod GitHub environment
• add a release-pipeline contract assertion that rejects the obsolete release environment

Root cause

The Rust publisher was the only job in release-baml-language.yml still targeting environment: release. That environment requires manual approval, so an otherwise automatic canary language release stopped at the crates.io publisher.

Impact

Future crates.io publishing jobs use the same Infisical-backed production environment as the rest of the release pipeline and no longer wait on the obsolete release approval gate. OIDC permissions and the crates.io trusted-publishing workflow identity are unchanged.

This cannot alter the already-started release run: GitHub reruns use the workflow definition from the original run SHA. That run must either receive approval for its existing release deployment or be superseded by a new post-merge canary release.

Validation

• python3 -m unittest scripts.tests.test_release_pipeline_contract (19 tests)
• actionlint .github/workflows/release-baml-language.yml
• YAML parse
• git diff --check
• repository pre-commit hooks

Summary by CodeRabbit

• Release Pipeline
  • Updated the crates.io publishing workflow to use the boundary-tools-prod release environment.
  • Added validation to ensure the publishing workflow continues using the correct environment.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
beps	Ready	Preview, Comment	Jul 25, 2026 1:10am
promptfiddle	Ready	Preview, Comment	Jul 25, 2026 1:10am
promptfiddle2	Ready	Preview, Comment	Jul 25, 2026 1:10am

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 41057469-ce79-4a8a-a3d7-14298cb985b0

📥 Commits

Reviewing files that changed from the base of the PR and between c966408 and 65a0256.

📒 Files selected for processing (2)

• .github/workflows/release-baml-language.yml
• scripts/tests/test_release_pipeline_contract.py

---

📝 Walkthrough

Walkthrough

The crates.io publishing job in the BAML language release workflow now uses the boundary-tools-prod environment. The release pipeline contract test captures this job and verifies that it does not use release.

Changes

Release environment configuration

Layer / File(s)	Summary
Crates.io publishing environment and contract validation .github/workflows/release-baml-language.yml, scripts/tests/test_release_pipeline_contract.py	The publish-crates-io job uses boundary-tools-prod, and the release contract test asserts this value while rejecting release.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Possibly related PRs

• BoundaryML/baml#3487: Adjusts release workflow environment configuration and removes reliance on environment: release.
• BoundaryML/baml#4134: Changes the publish-crates-io environment in the same release workflow.
• BoundaryML/baml#4158: Updates release pipeline contract validation around the publish-crates-io job.

Suggested reviewers: 2kai2kai2, atx24

Poem

I’m a rabbit hopping through the release gate,
Crates now bloom in boundary-tools-prod state.
The old release path stays out of sight,
Tests guard the workflow day and night.
Hop, hop—publishing is set just right!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly summarizes the main change: switching crates.io releases to the boundary-tools-prod environment.
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.

✨ 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 agent/use-boundary-tools-prod-for-crates

---

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	🔒 27.2 MB	11.6 MB	file	27.1 MB	+151.0 KB (+0.6%)	OK
✅	packed-program	Linux	🔒 17.6 MB	7.3 MB	file	17.6 MB	+7.2 KB (+0.0%)	OK
✅	baml-cli	macOS	🔒 21.2 MB	10.1 MB	file	21.0 MB	+149.1 KB (+0.7%)	OK
✅	packed-program	macOS	🔒 13.8 MB	6.4 MB	file	13.8 MB	+33.1 KB (+0.2%)	OK
✅	baml-cli	Windows	🔒 22.8 MB	10.3 MB	file	22.7 MB	+126.0 KB (+0.6%)	OK
✅	packed-program	Windows	🔒 14.7 MB	6.5 MB	file	14.7 MB	+4.6 KB (+0.0%)	OK
✅	bridge_wasm	WASM	16.5 MB	🔒 4.5 MB	gzip	4.5 MB	+18.7 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