engine: bump version to 0.224.0 - #4286
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe release updates version metadata from 0.223.0 to 0.224.0 across packages, integrations, editor extensions, and versioning configuration. Changelog entries were updated, generated client compatibility versions were synchronized, and the TypeScript integration-test report was regenerated. Changes0.224.0 release preparation
Estimated code review effort: 2 (Simple) | ~15 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
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 |
⏭️ 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-ad7214be-30da-46e5-bcc9-d2e54f15ce6f.docs.buildwithfern.com |
Signed-off-by: Sam Lijin <sam@boundaryml.com>
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 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`:
- Line 16: Rename the duplicated section heading from “Bug Fixes” to “Bug fixes”
in CHANGELOG.md lines 16-16 and fern/pages/changelog.mdx lines 18-18, preserving
the existing heading level and surrounding changelog content.
In `@integ-tests/typescript/junit.xml`:
- Line 2: Do not use the JUnit summary in integ-tests/typescript/junit.xml as
release validation; address the underlying non-environmental regressions
instead, including cached-token assertions expecting 0 rather than null,
enabling --experimental-vm-modules for the AWS Bedrock modular test, and fixing
the logger test’s 30-second timeout.
🪄 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: eb2c1877-3a55-49b0-86e9-126ea0cd5d20
⛔ 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
0.223.0to0.224.0after fix(openai): preserve content-block metadata on openai-responses (GPT-5.6 prompt_cache_breakpoint) #4155 merged.baml.unstable.string→string.frombreaking change and the OpenAI Responses API metadata fix from fix(openai): preserve content-block metadata on openai-responses (GPT-5.6 prompt_cache_breakpoint) #4155.Impact
Prepares the next full minor engine release across Python, TypeScript, Ruby, Go, Rust, VS Code, Zed, JetBrains, and integration-test version manifests.
Validation
cargo test -p baml-runtime responses_api --lib(4 passed)claude-3-haiku-20240307model, invalid AWS test credentials, and live-provider/test-environment failures; the generated JUnit report is committed.Generated with
tools/bump-versionand completed manually from its build step after bootstrapping the fresh clone's locked dependencies.Summary by CodeRabbit
Bug Fixes
baml testfrom hanging on self-referential environment variables.Release