Skip to content

engine: bump version to 0.226.0 - #4474

Merged
sxlijin merged 1 commit into
canaryfrom
sxlijin/Prepare-engine-0.226.0-release
Aug 17, 2026
Merged

sxlijin merged 1 commit into
canaryfrom
sxlijin/Prepare-engine-0.226.0-release

Conversation

@sxlijin

@sxlijin sxlijin commented Aug 17, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Release boundary

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

@coderabbitai

coderabbitai Bot commented Aug 17, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The release updates version references from 0.225.0 to 0.226.0 across package manifests, generated integration clients, version configuration, and release documentation.

Changes

0.226.0 Release

Layer / File(s) Summary
Release documentation
CHANGELOG.md, fern/pages/changelog.mdx
Adds the 0.226.0 release entry with connection pooling and OpenAI audio transcription features.
Package version declarations
engine/..., languages/rust/Cargo.toml, jetbrains/gradle.properties, typescript/apps/vscode-ext/package.json
Updates package, workspace, extension, gem, and language client versions to 0.226.0.
Generated clients and version configuration
integ-tests/..., tools/versions/*
Updates generated client versions, embedded generator fixtures, and bumpversion configuration to 0.226.0.

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

Merge Risk: ⚪ Minimal · up to 960dd

This PR updates the 0.226.0 release surfaces, regenerated clients, changelogs, and lockfiles, with the listed builds and targeted validations completed. No actionable merge-blocking risk remains beyond normal final checks and review.

Poem

A rabbit checks the version line,
“0.226.0” looks fine.
Clients and fixtures hop in tune,
Release notes shine like a moon.
All references match the sign!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely identifies the primary change: bumping the engine version to 0.226.0.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch sxlijin/Prepare-engine-0.226.0-release

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@sxlijin
sxlijin temporarily deployed to boundary-tools-dev August 17, 2026 20:54 — with GitHub Actions Inactive
@github-actions

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.

@github-actions

github-actions Bot commented Aug 17, 2026 •

Copy link
Copy Markdown

@vercel

vercel Bot commented Aug 17, 2026 •

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
beps Ready Ready Preview Aug 17, 2026 9:24pm
promptfiddle2 Ready Ready Preview Aug 17, 2026 9:24pm

Request Review

@vercel
vercel Bot temporarily deployed to Preview – beps August 17, 2026 20:55 Inactive
@sxlijin
sxlijin force-pushed the sxlijin/Prepare-engine-0.226.0-release branch from de9cfba to f43cec5 Compare August 17, 2026 20:58
@sxlijin
sxlijin temporarily deployed to boundary-tools-dev August 17, 2026 20:58 — with GitHub Actions Inactive
@vercel
vercel Bot temporarily deployed to Preview – beps August 17, 2026 20:59 Inactive
@sxlijin
sxlijin force-pushed the sxlijin/Prepare-engine-0.226.0-release branch from f43cec5 to 960dd5b Compare August 17, 2026 21:04
@sxlijin
sxlijin temporarily deployed to boundary-tools-dev August 17, 2026 21:04 — with GitHub Actions Inactive
@sxlijin

sxlijin commented Aug 17, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 17, 2026 •

Copy link
Copy Markdown
Contributor
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@vercel
vercel Bot temporarily deployed to Preview – beps August 17, 2026 21:06 Inactive

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔇 Additional comments (36)
CHANGELOG.md (1)

5-11: LGTM!

engine/Cargo.toml (1)

193-193: LGTM!

engine/language_client_go/baml_go/lib_common.go (1)

35-35: LGTM!

engine/language_client_python/pyproject.toml (1)

3-3: LGTM!

engine/language_client_ruby/baml.gemspec (1)

5-5: LGTM!

engine/language_client_typescript/package.json (1)

3-3: LGTM!

engine/zed/Cargo.toml (1)

6-6: LGTM!

engine/zed/extension.toml (1)

6-6: LGTM!

jetbrains/gradle.properties (1)

8-8: LGTM!

languages/rust/Cargo.toml (1)

15-15: LGTM!

Also applies to: 40-42

integ-tests/react/baml_client/index.ts (1)

24-28: LGTM!

Also applies to: 38-38

fern/pages/changelog.mdx (1)

7-13: LGTM!

typescript/apps/vscode-ext/package.json (1)

5-5: LGTM!

integ-tests/baml_src/generators.baml (1)

4-58: 🗄️ Data Integrity & Integration

⚠️ Unverified finding
Sandbox verification was unavailable.

Run the required BAML generation check.

From integ-tests/python, run:

Verify that the generated clients remain deterministic and contain version 0.226.0.

As per coding guidelines, run this command whenever integ-tests/baml_src/** changes.

integ-tests/go/baml_client/baml_source_map.go (1)

29-29: LGTM!

integ-tests/python-v1/baml_client/__init__.py (1)

13-13: LGTM!

integ-tests/python-v1/baml_client/inlinedbaml.py (1)

26-26: LGTM!

integ-tests/python/baml_client/__init__.py (1)

13-13: LGTM!

integ-tests/python/baml_client/inlinedbaml.py (1)

26-26: LGTM!

integ-tests/rust/src/baml_client/baml_source_map.rs (1)

40-40: 🎯 Functional Correctness

Run the required Rust test command before merge.

This Rust file changed. Run cargo test --lib and confirm that it passes.

As per coding guidelines: “Always run cargo test --lib if you changed any Rust code.”

Source: Coding guidelines

tools/versions/typescript.cfg (1)

2-2: LGTM!

tools/versions/vscode.cfg (1)

2-2: LGTM!

tools/versions/zed.cfg (1)

2-2: LGTM!

integ-tests/react/baml_client/inlinedbaml.ts (1)

34-34: LGTM!

integ-tests/typescript-esm/baml_client/index.ts (1)

24-28: LGTM!

Also applies to: 38-38

integ-tests/typescript-esm/baml_client/inlinedbaml.ts (1)

34-34: LGTM!

integ-tests/typescript/baml_client/index.ts (2)

24-28: LGTM!


38-38: LGTM!

integ-tests/typescript/baml_client/inlinedbaml.ts (1)

34-34: LGTM!

tools/versions/engine.cfg (1)

2-2: LGTM!

tools/versions/go.cfg (1)

2-2: LGTM!

tools/versions/integ-tests.cfg (1)

2-2: LGTM!

tools/versions/jetbrains.cfg (1)

2-2: LGTM!

tools/versions/python.cfg (1)

2-2: LGTM!

tools/versions/ruby.cfg (1)

2-2: LGTM!

tools/versions/rust.cfg (1)

2-2: LGTM!


ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c95d8645-5936-4666-8203-34d9bb69f62b

📥 Commits

Reviewing files that changed from the base of the PR and between 851e763 and 960dd5b.

⛔ Files ignored due to path filters (2)
  • engine/Cargo.lock is excluded by !**/*.lock
  • languages/rust/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (35)
  • CHANGELOG.md
  • engine/Cargo.toml
  • engine/language_client_go/baml_go/lib_common.go
  • engine/language_client_python/pyproject.toml
  • engine/language_client_ruby/baml.gemspec
  • engine/language_client_typescript/package.json
  • engine/zed/Cargo.toml
  • engine/zed/extension.toml
  • fern/pages/changelog.mdx
  • integ-tests/baml_src/generators.baml
  • integ-tests/go/baml_client/baml_source_map.go
  • integ-tests/python-v1/baml_client/__init__.py
  • integ-tests/python-v1/baml_client/inlinedbaml.py
  • integ-tests/python/baml_client/__init__.py
  • integ-tests/python/baml_client/inlinedbaml.py
  • integ-tests/react/baml_client/index.ts
  • integ-tests/react/baml_client/inlinedbaml.ts
  • integ-tests/rust/src/baml_client/baml_source_map.rs
  • integ-tests/typescript-esm/baml_client/index.ts
  • integ-tests/typescript-esm/baml_client/inlinedbaml.ts
  • integ-tests/typescript/baml_client/index.ts
  • integ-tests/typescript/baml_client/inlinedbaml.ts
  • jetbrains/gradle.properties
  • languages/rust/Cargo.toml
  • tools/versions/engine.cfg
  • tools/versions/go.cfg
  • tools/versions/integ-tests.cfg
  • tools/versions/jetbrains.cfg
  • tools/versions/python.cfg
  • tools/versions/ruby.cfg
  • tools/versions/rust.cfg
  • tools/versions/typescript.cfg
  • tools/versions/vscode.cfg
  • tools/versions/zed.cfg
  • typescript/apps/vscode-ext/package.json

Included review availability: Your plan includes up to 8 reviews per rolling hour; 1 remains after this review.

@vercel
vercel Bot temporarily deployed to Preview – promptfiddle2 August 17, 2026 21:14 Inactive
@sxlijin
sxlijin force-pushed the sxlijin/Prepare-engine-0.226.0-release branch from 960dd5b to e41c5b7 Compare August 17, 2026 21:14
@sxlijin
sxlijin temporarily deployed to boundary-tools-dev August 17, 2026 21:14 — with GitHub Actions Inactive
@sxlijin

sxlijin commented Aug 17, 2026

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 17, 2026 •

Copy link
Copy Markdown
Contributor
⚠️ Action not completed

No files to review.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

@vercel
vercel Bot temporarily deployed to Preview – beps August 17, 2026 21:15 Inactive
@vercel
vercel Bot temporarily deployed to Preview – promptfiddle2 August 17, 2026 21:24 Inactive
@sxlijin
sxlijin marked this pull request as ready for review August 17, 2026 21:55
@sxlijin
sxlijin added this pull request to the merge queue Aug 17, 2026
Merged via the queue into canary with commit 2fde4f7 Aug 17, 2026
48 checks passed
@sxlijin
sxlijin deleted the sxlijin/Prepare-engine-0.226.0-release branch August 17, 2026 22:20

This branch was previously deployed

3 inactive deployments
Preview – promptfiddle2 — e41c5b74 Deployed Aug 17, 2026 by vercel[bot]
Preview – beps — e41c5b74 Deployed Aug 17, 2026 by vercel[bot]
boundary-tools-dev — e41c5b74 Deployed Aug 17, 2026 by sxlijin via Docs / publish docs #8893
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