Skip to content

Release BAML 0.25.1 with wrapper 0.3.1 - #5555

Merged
rossirpaulo merged 1 commit into
canaryfrom
rossirpaulo/release-0.25.1
Nov 6, 2026
Merged

rossirpaulo merged 1 commit into
canaryfrom
rossirpaulo/release-0.25.1

Conversation

@rossirpaulo

@rossirpaulo rossirpaulo commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

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 #5551 (run 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

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.

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]>
@vercel

vercel Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated
developer-docs Ready Ready Preview Nov 6, 2026 3:28am UTC

Request Review

@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

⏭️ 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.

@coderabbitai

coderabbitai Bot commented Nov 6, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

Version metadata changes to 0.25.1 across release settings and language SDKs. The baml package version changes to 0.3.1.

Changes: Release and SDK version alignment

Layer / File(s) Summary
Release version metadata
baml_language/crates/baml/Cargo.toml, baml_language/crates/baml_version/src/lib.rs, baml_language/release.toml
The baml package version changes to 0.3.1. The canonical, PyPI, stable, and canary version values change to 0.25.1.
SDK package and runtime versions
baml_language/sdks/cpp/bridge_cpp/include/baml/version.h, baml_language/sdks/csharp/bridge_csharp/src/*, baml_language/sdks/go/baml_go/version.go, baml_language/sdks/java/baml_bridge/src/main/java/baml_bridge/BamlVersion.java, baml_language/sdks/python/{pyproject.toml,src/baml_bridge/__init__.py}, baml_language/sdks/ruby/bridge_ruby/lib/baml/bridge/version.rb, baml_language/sdks/rust/bridge_rust/{Cargo.toml,src/version.rs}, baml_language/sdks/swift/Sources/BamlBridge/RuntimeIdentity.swift, baml_language/sdks/typescript/bridge_typescript/{package.json,src/version.rs}, baml_language/sdks/typescript/bridge_typescript_web/{package.json,src/version.rs}, typescript2/app-vscode-ext/package.json
SDK package version declarations and bridge runtime identity values change to 0.25.1. The VS Code extension package version also changes to 0.25.1.

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

Change: Other

Possibly related PRs

  • BoundaryML/baml#5483: Prepares wrapper 0.3.0 and adds a release check; this PR updates the wrapper to 0.3.1.

Suggested reviewers: sxlijin

Merge Risk: Minimal · up to 16c2d

The version updates appear consistent, with no merge-blocking issue identified.

Pre-merge checks: Passed 5

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title accurately summarizes the BAML and wrapper version bumps.
Docstring Coverage Passed 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 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.
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. (8 skipped: 8 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.

RuboCop (1.92.0)

baml_language/sdks/ruby/bridge_ruby/lib/baml/bridge/version.rb

invalid byte sequence in US-ASCII
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:181:in 'Regexp#match'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:181:in 'String#match'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:181:in 'RuboCop::TargetRuby::RubyVersionFile#find_version'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:31:in 'RuboCop::TargetRuby::Source#initialize'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:295:in 'Class#new'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:295:in 'block in RuboCop::TargetRuby#source'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:295:in 'Array#each'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:295:in 'Enumerator#each'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/target_ruby.rb:295:i

... [truncated 2433 characters] ...

ems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/config_store.rb:29:in 'RuboCop::ConfigStore#apply_options!'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/cli.rb:168:in 'RuboCop::CLI#act_on_options'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/cli.rb:50:in 'block in RuboCop::CLI#run'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/cli.rb:89:in 'RuboCop::CLI#profile_if_needed'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/lib/rubocop/cli.rb:46:in 'RuboCop::CLI#run'
/usr/local/lib/ruby/gems/3.4.0/gems/rubocop-1.92.0/exe/rubocop:15:in '<top (required)>'
/usr/local/lib/ruby/site_ruby/3.4.0/rubygems.rb:305:in 'Kernel#load'
/usr/local/lib/ruby/site_ruby/3.4.0/rubygems.rb:305:in 'Gem.activate_and_load_bin_path'
/usr/local/bin/rubocop:25:in '

'

Warning

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 each version line,
The numbers now align.
The bridge signs “0.25.1,”
The packages follow in time.
One small hop, release is done.

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: 69a7c14e-8ce3-4fc6-ae95-c588de9a1c5d
Commits

Reviewing files that changed from the base of the PR and between a2f6d54 and 16c2dbe.

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/**
Files selected for processing: 19

  • baml_language/crates/baml/Cargo.toml
  • baml_language/crates/baml_version/src/lib.rs
  • baml_language/release.toml
  • baml_language/sdks/cpp/bridge_cpp/include/baml/version.h
  • baml_language/sdks/csharp/bridge_csharp/src/Baml.Bridge.csproj
  • baml_language/sdks/csharp/bridge_csharp/src/RuntimeIdentity.cs
  • baml_language/sdks/go/baml_go/version.go
  • baml_language/sdks/java/baml_bridge/src/main/java/baml_bridge/BamlVersion.java
  • baml_language/sdks/python/pyproject.toml
  • baml_language/sdks/python/src/baml_bridge/__init__.py
  • baml_language/sdks/ruby/bridge_ruby/lib/baml/bridge/version.rb
  • baml_language/sdks/rust/bridge_rust/Cargo.toml
  • baml_language/sdks/rust/bridge_rust/src/version.rs
  • baml_language/sdks/swift/Sources/BamlBridge/RuntimeIdentity.swift
  • baml_language/sdks/typescript/bridge_typescript/package.json
  • baml_language/sdks/typescript/bridge_typescript/src/version.rs
  • baml_language/sdks/typescript/bridge_typescript_web/package.json
  • baml_language/sdks/typescript/bridge_typescript_web/src/version.rs
  • typescript2/app-vscode-ext/package.json

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.

@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown

Binary size checks failed

❌ 2 violations · ✅ 1 passed

⚠️ 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)

Add/update baselines:

.ci/size-gate/wasm32-unknown-unknown.toml:

[artifacts.bridge_wasm]
file_bytes = 26012755
gzip_bytes = 7684738

.ci/size-gate/x86_64-unknown-linux-gnu.toml:

[artifacts.packed-program]
file_bytes = 39141528
gzip_bytes = 16087446

Generated by cargo size-gate · workflow run

@rossirpaulo
rossirpaulo added this pull request to the merge queue Nov 6, 2026
Merged via the queue into canary with commit 6a3eb3d Nov 6, 2026
102 checks passed
@rossirpaulo
rossirpaulo deleted the rossirpaulo/release-0.25.1 branch November 6, 2026 04:04

This branch was successfully deployed

1 active deployment
Preview – developer-docs — 16c2dbe1 Deployed Nov 6, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant