[deanrie]

What

pyproject.toml pins protobuf>=5.29.4,<7, and src/xai_sdk/proto/__init__.py routes only major == 6 to the 6.x generated modules, raising ValueError("Unsupported protobuf version") for anything newer. An environment that already has protobuf 7 cannot resolve the SDK at all; the resolver stops at the pin before any code runs.

Why the 6.x gencode is enough

protobuf's runtime check (google.protobuf.runtime_version.ValidateProtobufRuntimeVersion, 7.36.2) refuses two things: a gencode/runtime domain mismatch, and a runtime that is older than the gencode it loads. A newer runtime loading older gencode is the supported direction, so the modules generated with 6.30.0 import on 7.x without a warning. No regenerated stubs are needed.

Change

• protobuf>=5.29.4,<8 in pyproject.toml (and the matching requires-dist line in uv.lock; the resolved dev version is unchanged).
• _PROTOBUF_MAJOR >= 6 selects the v6 modules; == 5 and the ValueError for older runtimes are unchanged.
• CHANGELOG entry under Unreleased / Changed.

Verification

• Full suite under protobuf 6.31.1 (project venv): 867 passed.
• Full suite under protobuf 7.36.2 (separate venv, uv pip install -e . 'protobuf>=7,<8'): 867 passed, and -W error::UserWarning stays green, so the 7.x runtime emits no gencode warnings for the v6 modules.
• tests/proto_test.py reloads xai_sdk.proto with the runtime version patched: 7.0.0, 7.36.0 and 8.1.0 select v6 (these three fail on main with the ValueError), 6.31.1 selects v6, 5.29.4 selects v5, 4.25.0 is still rejected.
• ruff check, ruff format --check, pyright clean.

#224 carries the same two-line change as its first commit (cherry-picked from #183). If this one lands first I drop that commit from #224; if #224 lands first this PR reduces to the test file and the CHANGELOG line.

[Omar-V2]

This has been addressed by #223 and is fixed in versions 1.21.0 and above