You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Bump CREATE_SUB_ORGANIZATION to V8 and CREATE_USERS to V4 #23
The TypeScript SDK pins CREATE_SUB_ORGANIZATION to V8 and CREATE_USERS to V4. The Python client keeps V7 and V3 so that #20 does not change behavior for existing callers.
Follow-up: move the pins to V8 and V4 in codegen/http/generate_http.py and codegen/types/generate_types.py, regenerate, and record the body shape changes in the changeset. Check the createSubOrganizationResultV8 and createUsersResultV4 result keys unpack.
One more divergence to decide alongside V8/V4, raised in the adversarial review of #20: Python sends CREATE_SWAP_QUOTE_V3 while the TypeScript SDK pins V2. Python's result key (createSwapQuoteResultV2) matches what the backend writes for V3, so it works; the question is whether the two SDKs should agree. #20 now pins the three activities it moved and adds codegen/activity_versions.json, so any future move shows up as a snapshot diff.
Activity
figitaki commentedon Oct 17, 2026
One more divergence to decide alongside V8/V4, raised in the adversarial review of #20: Python sends CREATE_SWAP_QUOTE_V3 while the TypeScript SDK pins V2. Python's result key (createSwapQuoteResultV2) matches what the backend writes for V3, so it works; the question is whether the two SDKs should agree. #20 now pins the three activities it moved and adds codegen/activity_versions.json, so any future move shows up as a snapshot diff.