Repository navigation
Release BAML 0.25.1 with wrapper 0.3.1 - #5555
Conversation
The 0.25.0 canary release stopped at "Publish wrapper release assets": the baml-wrapper-0.3.0 tag already points at the failed 0.24.0 release commit. Bump the wrapper so this release can publish it, and the language version so the bump starts a canary release (RELEASING.md). Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
⏭️ Performance benchmarks were skippedPerf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to To run them on this PR, do any of the following, then push a commit (or re-run CI):
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Binary size checks failed❌ 2 violations · ✅ 1 passed
Details & how to fixViolations:
Add/update baselines:
[artifacts.bridge_wasm]
file_bytes = 26012755
gzip_bytes = 7684738
[artifacts.packed-program]
file_bytes = 39141528
gzip_bytes = 16087446Generated by |
Bumps the BAML wrapper from 0.3.0 to 0.3.1 and the language from 0.25.0 to 0.25.1, using
scripts/baml-wrapper-version bump --patchandscripts/baml-language-version bump --patch. Only version strings change, and bothcheckcommands pass.The 0.25.0 canary release from #5551 (run 42150548387) failed at "Publish wrapper release assets":
The failed 0.24.0 release had created that tag before its Homebrew step failed. Because of this failure:
pkg.boundaryml.commanifests, docs, Homebrew, AUR and winget steps were skipped.RELEASING.md says to bump the wrapper version, and to bump the language version as well so the merge starts a canary release.
🤖 Generated with Claude Code
Summary by CodeRabbit