bump to 0.2.12

[tleyden]

No description provided.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one) (1)

• code-rabbit-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: ac363d1a-8710-4c23-af5a-96b3230a5924

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump_version_0_2_12

---

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.}

[greptile-apps]

Greptile Summary

This PR bumps Brain3 from 0.2.11 to 0.2.12 across release-facing files.

• Rust package metadata and Cargo.lock updated to 0.2.12.
• Python package metadata, lockfile, and startup test expectations updated to 0.2.12.
• README install URL and runtime release constant updated to v0.2.12.

Confidence Score: 5/5

This looks safe to merge after checking the release artifacts are published in step with the version bump.

The version strings are internally consistent across the changed files.

README.MD and crates/core/src/application/first_run_setup.rs need release-order attention for the installer URL and default container image tag.

T-Rex Logs

What T-Rex did

• I created and used a CPython 3.14.6 environment, installed the package from the local project, and ran 5 tests that all passed with exit code 0.
• I executed the Python MCP version smoke test and observed package_version=0.2.12, console_entry_points mapping brain3-mcp-vault-tools=brain3_mcp_vault_tools.server:main, package_version_func=0.2.12, mcp_host=127.0.0.1, mcp_port=2765, and exit code 0.
• I noted the exact smoke script used for the metadata/import validation, named python-mcp-version-smoke.py.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
apps/gateway/Cargo.toml	Updates the gateway package version to 0.2.12.
crates/core/src/application/first_run_setup.rs	Updates the runtime release constant used for default release-tagged assets.
brain3-mcp-vault-tools/pyproject.toml	Updates the Python MCP vault tools package version to 0.2.12.
brain3-mcp-vault-tools/uv.lock	Updates the Python lockfile package version to match pyproject.toml.
README.MD	Updates the install command to the v0.2.12 release path.
brain3-mcp-vault-tools/tests/test_server_startup.py	Updates startup log test expectations to 0.2.12.
Cargo.lock	Updates the locked brain3 package version to 0.2.12.

_{Reviews (1): Last reviewed commit: "bump to 0.2.12" | Re-trigger Greptile}

[greptile-apps]

Versioned Installer Can Lead Release

When this README lands on main before the matching release artifacts are published, the documented install command points new users at the v0.2.12 S3 path immediately. If that path is not available yet, the primary install command fails with an HTTP error instead of installing Brain3.

[greptile-apps]

Default Container Tag Can Lead Image

CURRENT_RELEASE feeds the default MCP container image tag used during first-run setup. If the binary release is published before ghcr.io/tleyden/brain3-mcp-vault-tools:v0.2.12 is available, a fresh install that leaves the container image tag empty will try to pull that tag and fail setup with a missing manifest or pull error.