You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bumps the BAML language version from 0.24.0 to 0.25.0 with scripts/baml-language-version bump --minor. Only version strings change: 20 files, and baml-language-version check passes.
The 0.24.0 canary release (run 42111122075) failed at "Publish Homebrew wrapper formula" with "Refusing to load formula boundaryml/tap/baml from untrusted tap". #5546 fixed that. Because of the failure:
PyPI, npm and crates.io have 0.24.0.
The Go SDK mirror, the pkg.boundaryml.com manifests and the developer docs were not published.
The canary channel was not promoted.
Rather than re-run 0.24.0, this releases 0.25.0 from current canary. That includes #5546 and the package_name setting (#5532, #5533).
For the release oncall: the 0.3.0 wrapper got its GitHub release before the Homebrew step failed. RELEASING.md says a language release republishes the wrapper only when its version differs from the published one, so check that this release still publishes the Homebrew formula.
The 0.24.0 canary release failed at the Homebrew wrapper step (fixed by
#5546), so Go was not published and the canary channel was not promoted.
Release the next version instead.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
No actionable comments were generated in the recent review.
Walkthrough
Release metadata, bridge SDK package versions, runtime identity constants, and the VS Code extension version change from 0.24.0 to 0.25.0. The canary channel remains unchanged.
Changes: Version alignment
Layer / File(s)
Summary
Release, SDK, and extension version updates baml_language/crates/baml_version/src/lib.rs, baml_language/release.toml, baml_language/sdks/*, typescript2/app-vscode-ext/package.json
Release metadata, SDK package versions, runtime version constants, and the VS Code extension version change to 0.25.0.
BoundaryML/baml#5483: Prepares the 0.24.0 toolchain release; this PR updates the toolchain and wrapper version declarations to 0.25.0.
Suggested reviewers:sxlijin
Merge Risk: Minimal · up to 5e2e9
This release bump only changes version identifiers across the release metadata, SDK packages, runtime constants and the VS Code extension. No concrete merge-blocking issue was found. The release oncall should still confirm the wrapper and Homebrew state when running the release.
Pre-merge checks: 5
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title clearly describes the version update to BAML 0.25.0.
Docstring Coverage
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 11 files. (7 skipped: 7 unsupported.)
Finishing Touches
Generate docstrings
Commit to this branch
Create a new PR
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Warning
Some tools did not complete. Review the errors below.
Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.
A rabbit checks the version line, Each bridge now reads point twenty-five. The release notes hop into place, The canary keeps its steady pace. I nibble clover, pleased to see All package tags agree with me.
Recent review info
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Repository UI
Review profile: CHILL
Plan: Advanced
Run ID: b7f757f9-4481-40e6-8133-10ec3d1514dd
Commits
Reviewing files that changed from the base of the PR and between 8de3960 and 5e2e95b.
Files ignored due to path filters: 2
baml_language/Cargo.lock is excluded by !**/*.lock
baml_language/sdks/typescript/bridge_typescript/dist/native.js is excluded by !**/dist/**
Included review availability: This review used your included allowance. 7 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 10 reviews per hour.
⚠️ Please fix the size gate issues or acknowledge them by updating baselines.
Artifact
Platform
File
Gzip
Gated on
Baseline
Delta
Status
✅
baml-cli
Linux
🔒 64.7 MB
27.5 MB
file
73.1 MB
-8.4 MB (-11.5%)
OK
❌
packed-program
Linux
🔒 39.1 MB
16.1 MB
file
29.2 MB
+10.0 MB (+34.3%)
FAIL
❌
bridge_wasm
WASM
26.0 MB
🔒 7.7 MB
gzip
5.7 MB
+2.0 MB (+35.7%)
FAIL
🔒 = 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.
Details & how to fix
Violations:
packed-program (Linux) file_bytes: 39.1 MB exceeds limit of 30.1 MB (exceeded by +9.0 MB, policy: max_file_bytes)
packed-program (Linux) file_delta_pct: +34.3% exceeds limit of 3.0% (exceeded by +31.3pp, policy: max_delta_pct)
bridge_wasm (WASM) gzip_bytes: 7.7 MB exceeds limit of 5.9 MB (exceeded by +1.8 MB, policy: max_gzip_bytes)
bridge_wasm (WASM) gzip_delta_pct: +35.7% exceeds limit of 3.0% (exceeded by +32.7pp, policy: max_delta_pct)
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 --patch` and
`scripts/baml-language-version bump --patch`. Only version strings
change, and both `check` commands pass.
The 0.25.0 canary release from BoundaryML#5551 ([run
42150548387](https://github.com/BoundaryML/baml/actions/runs/42150548387))
failed at "Publish wrapper release assets":
> wrapper tag baml-wrapper-0.3.0 points to
dec4713, expected
a2f6d54; bump the wrapper version
The failed 0.24.0 release had created that tag before its Homebrew step
failed. Because of this failure:
- PyPI, npm and crates.io have 0.25.0.
- The Go mirror, `pkg.boundaryml.com` manifests, docs, Homebrew, AUR and
winget steps were skipped.
- The canary channel was not promoted.
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](https://claude.com/claude-code)
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
<!-- coderabbit-ai-generated:v1 -->
## Summary by CodeRabbit
* **Release**
* Updated the BAML toolchain and bridge runtime to version 0.25.1 across
supported language SDKs and the VS Code extension.
* Updated the BAML package to version 0.3.1.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Co-authored-by: Claude Opus 5.5 <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Bumps the BAML language version from 0.24.0 to 0.25.0 with
scripts/baml-language-version bump --minor. Only version strings change: 20 files, andbaml-language-version checkpasses.The 0.24.0 canary release (run 42111122075) failed at "Publish Homebrew wrapper formula" with "Refusing to load formula boundaryml/tap/baml from untrusted tap". #5546 fixed that. Because of the failure:
pkg.boundaryml.commanifests and the developer docs were not published.Rather than re-run 0.24.0, this releases 0.25.0 from current canary. That includes #5546 and the
package_namesetting (#5532, #5533).For the release oncall: the 0.3.0 wrapper got its GitHub release before the Homebrew step failed. RELEASING.md says a language release republishes the wrapper only when its version differs from the published one, so check that this release still publishes the Homebrew formula.
🤖 Generated with Claude Code
Summary by CodeRabbit