Sync CLI version reporting with package release

[skeehn]

Problem

The Rust CLI had drifted from the Python package release version. chromadb/__init__.py reports 1.5.7, but the CLI crate and clap metadata still reported 1.4.3.

That means chroma --version can misreport the release version, which is confusing for users, support, and release verification.

Fix

• bump rust/cli/Cargo.toml to 1.5.7
• change the clap annotation in rust/cli/src/lib.rs to use the crate version instead of a hardcoded string
• update RELEASE_PROCESS.md so releases bump both the Python package version and the CLI crate version
• refresh Cargo.lock so the chroma-cli package entry matches the crate version

Why this is safe

This PR only changes version/reporting and release documentation. It does not change DB, query, persistence, or storage behavior.

Verification

• rebuilt the local runtime artifacts from source and verified PYTHONPATH=$PWD ./.venv/bin/chroma --version prints chroma 1.5.7
• PYTHONPATH=$PWD ./.venv/bin/pytest chromadb/test/test_client.py::test_ephemeral_client chromadb/test/test_client.py::test_persistent_client_context_manager chromadb/test/test_cli.py::test_app -q -> 3 passed in 7.35s
• PYTHONPATH=$PWD ./.venv/bin/pytest chromadb/test/test_client.py::test_persistent_client chromadb/test/test_client.py::test_persistent_client_close chromadb/test/test_client.py::test_persistent_client_context_manager chromadb/test/test_client.py::test_ephemeral_client_close chromadb/test/test_client.py::test_ephemeral_client_context_manager -q -> 5 passed in 0.97s
• manual embedded PersistentClient run with deterministic embeddings: create/add/query/count passed and persisted data survived reopen
• manual chroma run --host 127.0.0.1 --path /tmp/chroma-manual-http --port 8013 + HttpClient run: heartbeat, create, add, query, and count passed
• manual HTTP persistence restart check passed: after restarting the server, the collection still returned count 3 and the same nearest neighbors
• cargo check -p chroma-cli passed on the pinned Rust 1.92.0 toolchain in 1m 46s

Notes

I also tried a broader chromadb/test/test_api.py slice, but that local invocation failed in fixture setup (fastapi, sqlite_fixture, etc. missing), which appears to be a harness-selection issue rather than a regression from this change.

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

Review found no issues; version alignment and release-process updates appear correct and low risk.

Status: No Issues Found | Risk: Low

Review Details

📁 4 files reviewed | 💬 0 comments

[propel-code-bot]

Align chroma-cli version output with package release version

This PR fixes CLI version drift by updating rust/cli/Cargo.toml from 1.4.3 to 1.5.7 and switching clap metadata in rust/cli/src/lib.rs from a hardcoded #[command(version = "1.4.3")] to #[command(version)]. This ensures chroma --version reflects the crate/package version automatically going forward.

It also updates RELEASE_PROCESS.md to require bumping both chromadb/__init__.py and rust/cli/Cargo.toml during releases, and refreshes Cargo.lock so the chroma-cli lock entry matches the crate version. Changes are scoped to version/reporting and release process documentation.

This summary was automatically generated by @propel-code-bot