release: prepare baml_language 0.18.0 release - #4629
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
⏭️ 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. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (2)
📒 Files selected for processing (18)
Included review availability: Your plan provides up to 8 included reviews per hour; 5 remain after this review. 📝 WalkthroughWalkthroughThe release configuration, SDK runtime identities, package metadata, and VS Code extension version are updated from 0.17.0 to 0.18.0. ChangesVersion alignment
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This PR synchronizes the BAML language and SDK/runtime identities to 0.18.0 and is covered by the listed validation checks; no actionable merge-blocking risk remains beyond normal release approval. Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 5 functions across 11 files. (7 skipped: 7 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Warning Some tools did not complete. Review the errors below. 🔧 RuboCop (1.89.0)baml_language/sdks/ruby/bridge_ruby/lib/baml/bridge/version.rbinvalid byte sequence in US-ASCII ... [truncated 2433 characters] ... ems/3.4.0/gems/rubocop-1.90.0/lib/rubocop/config_store.rb:29:in 'RuboCop::ConfigStore#apply_options!' 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 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 5cafa7fd03
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| pub const CANONICAL_VERSION: &str = "0.17.0"; | ||
| pub const PYPI_VERSION: &str = "0.17.0"; | ||
| pub const CANONICAL_VERSION: &str = "0.18.0"; |
There was a problem hiding this comment.
Refresh the program identity golden for 0.18.0
When the canonical version becomes 0.18.0, bex_vm_types/src/identity.rs still gates its cross-platform golden assertion on CANONICAL_VERSION == "0.17.0", so the assertion is skipped in every 0.18.0 test run. That test explicitly says its expected hash must be regenerated on a version bump; update its version guard and expected digest so changes to the program-identity framing remain covered.
Useful? React with 👍 / 👎.
Binary size checks passed✅ 7 passed
Generated by |
Summary
0.18.0.baml_language/release.tomlfrom0.17.0to0.18.0.Release safety
Merging this PR into
canarywill dispatch the productionbaml_language0.18.0 release workflow. No release, tag, package, artifact, or workflow was triggered while preparing this PR.Testing
scripts/baml-language-version checkscripts/baml-language-version showscripts/baml-language-version compute --channel canaryscripts/baml-language-version compute --channel canary --pypipython3 -m unittest scripts.tests.test_baml_language_version scripts.tests.test_release_pipeline_contractcargo test --manifest-path baml_language/Cargo.toml -p baml_versionmise run validate-markdown(frombaml_language)git diff --checkSummary by CodeRabbit