engine: bump version to 0.225.0 - #4310
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
📝 WalkthroughWalkthroughRelease metadata and package surfaces were updated from 0.224.0 to 0.225.0. Generated integration clients and generator fixtures were synchronized. Changelog entries document the 0.225.0 release. ChangesRelease version alignment
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 RuboCop (1.88.2)engine/language_client_ruby/baml.gemspecinvalid byte sequence in US-ASCII ... [truncated 1800 characters] ... cop-1.88.2/lib/rubocop/config_store.rb:34:in 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. Comment |
GitHub Actions
Inactive
⏭️ 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):
|
|
🌿 Preview your docs: https://boundary-preview-ca9091e5-86a5-4a92-a98c-17ba6e5ba3e5.docs.buildwithfern.com |
Signed-off-by: Sam Lijin <sam@boundaryml.com>
sxlijin
changed the title
GitHub Actions
Inactive
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
integ-tests/typescript/junit.xml (1)
2-135: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick winConsider not tracking generated test reports with volatile, environment-specific content.
This
junit.xmlembeds local absolute paths from the machine that generated it (for example/private/tmp/baml-bump-0.225.0.ehumKA/...) along with timestamps and durations that change on every run. Committing this generated artifact to version control produces noisy diffs on every regeneration and ties the report to one contributor's local build layout.Track this report as a CI-produced artifact instead of a versioned file, or add it to
.gitignore.Also applies to: 146-689
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@integ-tests/typescript/junit.xml` around lines 2 - 135, Remove the generated junit.xml report from version control and add its filename or report pattern to .gitignore so future test runs do not recreate tracked volatile output. Keep CI responsible for producing and publishing the JUnit report as an artifact.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 5-10: Complete the 0.225.0 section in CHANGELOG.md by adding the
matching Bug Fixes, Features, and Miscellaneous Chores entries from the Fern
changelog, preserving the existing release-note formatting and Docs entry.
---
Nitpick comments:
In `@integ-tests/typescript/junit.xml`:
- Around line 2-135: Remove the generated junit.xml report from version control
and add its filename or report pattern to .gitignore so future test runs do not
recreate tracked volatile output. Keep CI responsible for producing and
publishing the JUnit report as an artifact.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 8fbac1a7-b14e-4c3e-9018-bb2bf6890ac4
⛔ Files ignored due to path filters (1)
engine/Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (36)
CHANGELOG.mdengine/Cargo.tomlengine/language_client_go/baml_go/lib_common.goengine/language_client_python/pyproject.tomlengine/language_client_ruby/baml.gemspecengine/language_client_typescript/package.jsonengine/zed/Cargo.tomlengine/zed/extension.tomlfern/pages/changelog.mdxinteg-tests/baml_src/generators.bamlinteg-tests/go/baml_client/baml_source_map.gointeg-tests/python-v1/baml_client/__init__.pyinteg-tests/python-v1/baml_client/inlinedbaml.pyinteg-tests/python/baml_client/__init__.pyinteg-tests/python/baml_client/inlinedbaml.pyinteg-tests/react/baml_client/index.tsinteg-tests/react/baml_client/inlinedbaml.tsinteg-tests/rust/src/baml_client/baml_source_map.rsinteg-tests/typescript-esm/baml_client/index.tsinteg-tests/typescript-esm/baml_client/inlinedbaml.tsinteg-tests/typescript/baml_client/index.tsinteg-tests/typescript/baml_client/inlinedbaml.tsinteg-tests/typescript/junit.xmljetbrains/gradle.propertieslanguages/rust/Cargo.tomltools/versions/engine.cfgtools/versions/go.cfgtools/versions/integ-tests.cfgtools/versions/jetbrains.cfgtools/versions/python.cfgtools/versions/ruby.cfgtools/versions/rust.cfgtools/versions/typescript.cfgtools/versions/vscode.cfgtools/versions/zed.cfgtypescript/apps/vscode-ext/package.json
## Summary - bump all legacy BAML v0 release surfaces from 0.225.0 to 0.226.0 using the repository version-bump configuration - add exactly the two verified external-contributor engine changes: connection pooling from BoundaryML#3975 and OpenAI transcriptions from BoundaryML#4202 - synchronize the new 0.226.0 sections in the top-level and Fern changelogs - regenerate all nine integration clients without test-report churn and update the engine, Rust SDK, and generated Rust integration lockfile versions ## Release boundary - 0.225.0 boundary: release PR BoundaryML#4310 / merge commit da2a673 - BoundaryML#3975 shipped as 521919c - BoundaryML#4202 merged from reviewed head ff96fd4 as squash commit 79b8705; the reviewed-head and squash diffs have the same stable patch ID - BoundaryML#4464 and its byte-perfect revert BoundaryML#4469 have zero net diff and are excluded - rebased onto current canary after BoundaryML#4202 merged ## Validation - TypeScript runtime build and nine-client generation - Python runtime build/install and nine-client generation - deterministic regeneration: unchanged binary diff hash on repeated generation - locked Cargo metadata for the engine and Rust SDK workspaces - generated Rust integration library build: `cargo test --lib --locked` - OpenAI transcription wiremock closure tests: 2 passed - generated Python multipart request test: 1 passed - connection pooling transport test: 1 passed - HTTP config validation fixtures: 8 passed - release metadata and workflow contracts: 50 passed - stale 0.225.0 audit clean across release-owned surfaces; historical junit.xml intentionally unchanged - final release diff matches the 0.225.0 workflow-owned file set, excludes junit.xml test-report churn, and additionally refreshes the two tracked Rust SDK/integration lockfiles proven stale by locked builds ## Status - dependency satisfied; rebased onto current canary with the reviewed BoundaryML#4202 patch present - all required GitHub Actions checks are green; local and GitHub CodeRabbit reviews are green with approval and no review threads or requested changes - merge-ready; awaiting normal human review
1 participant
Summary
tools/bump-version.pyValidation
Generated with the repository's version-bump workflow.
Summary by CodeRabbit
New Features
Documentation
Chores