bumped patch version

[rossirpaulo]

Summary by CodeRabbit

• Chores
  • Bumped version from 0.12.0 to 0.12.1 across all SDKs and tools, including Python SDK, Node.js SDK, and VS Code extension.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
beps	Ready	Preview, Comment	Jun 12, 2026 5:34pm
promptfiddle	Ready	Preview, Comment	Jun 12, 2026 5:34pm
promptfiddle2	Ready	Preview, Comment	Jun 12, 2026 5:34pm

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 070657b7-48fd-4c59-9660-81cf373fcc40

📥 Commits

Reviewing files that changed from the base of the PR and between 2c01605 and 290c178.

📒 Files selected for processing (6)

• baml_language/crates/baml_version/src/lib.rs
• baml_language/release.toml
• baml_language/sdks/nodejs/bridge_nodejs/package.json
• baml_language/sdks/python/pyproject.toml
• baml_language/sdks/python/src/baml_core/__init__.py
• typescript2/app-vscode-ext/package.json

---

📝 Walkthrough

Walkthrough

Version identifiers for the BAML language toolchain are incremented from 0.12.0 to 0.12.1 across Rust version constants, release configuration, Python and Node.js SDK package manifests, the Python SDK runtime constant, and the VS Code extension package manifest.

Changes

Version bump to 0.12.1

Layer / File(s)	Summary
Version surfaces across Rust, Python, Node.js, and VS Code baml_language/crates/baml_version/src/lib.rs, baml_language/release.toml, baml_language/sdks/python/pyproject.toml, baml_language/sdks/python/src/baml_core/__init__.py, baml_language/sdks/nodejs/bridge_nodejs/package.json, typescript2/app-vscode-ext/package.json	Rust version constants (CANONICAL_VERSION, PYPI_VERSION, STABLE_VERSION), release configuration, and SDK/extension package version fields are all updated from 0.12.0 to 0.12.1 in a coordinated single bump.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• BoundaryML/baml#3738: Previous version bump that updated the same version constants and manifests across the codebase.
• BoundaryML/baml#3679: Prior version bump updating the identical set of release and package version sources.
• BoundaryML/baml#3502: Updates Python SDK baml_language/sdks/python/pyproject.toml package version alongside other version configuration changes.

Poem

🐰 The version numbers all align,
From zero-twelve point zero to point-one so fine!
Across all the lands—Rust, Python, and more,
Each SDK and extension gets bumped to its core. ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'bumped patch version' directly and accurately describes the main change: updating version constants from 0.12.0 to 0.12.1 across multiple files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ 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 paulo/release-0.12.1

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

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

No description provided.