Phase 1: bump roe-ai to 1.0.802 (public SDK sync)#41
Conversation
Joins the synced 4-package family (roe-ai, roe-typescript, roe-golang/v2, roe-mcp) on a shared 2.0.0 baseline. No API surface changes — code that worked on 1.0.79 / 1.0.80 / 1.0.801 works on 2.0.0 unchanged. Why: the previous sub-patch versioning (1.0.811, 1.0.801) permanently shadowed future weekly releases because PyPI compares patches as integers (1.0.811 > 1.0.82). Resetting to a clean major + letting roe-main's release fan-out auto-bump the patch via `roe-sdk compute-next-version` makes the shadowing problem structurally impossible. Sibling PRs in the synced 4-package land: - roe-ai/roe-mcp: Phase 1+2 bootstrap contract + 2.0.0 bump - roe-ai/roe-typescript: Phase 1 1.0.80 -> 2.0.0 - roe-ai/roe-golang: Phase 1 1.0.80 -> 2.0.0 (v2 module path) - roe-ai/roe-main: Phase 3+4 adds mcp to targets.yml + the compute-sdk-version job that drives synced patch bumps.
Greptile SummaryThis PR retargets the SDK sync from
Confidence Score: 5/5Safe to merge — all MCP-facing wrappers, idempotency header propagation, and file-close lifecycle are correctly implemented and covered by unit tests. The idempotency header wiring in call_dynamic is correct, the generated facades translate errors uniformly through translate_response, and the CI drift check now gates against wrapper/spec divergence. The only gaps are test coverage for run_version idempotency key and a missing 400-error case for the tables upload, neither of which reflects a defect in the shipped code. No files require special attention; the two test coverage gaps noted are in tests/unit/test_agents_wrapper_transport.py and tests/unit/test_tables.py. Important Files Changed
Reviews (6): Last reviewed commit: "fix: retarget SDK sync release to 1.0.82" | Re-trigger Greptile |
|
@greptileai final review please. Included in the synced release fan-out drill: Python no-op spec stayed unchanged, synthetic SDK-visible operations generated into roe._generated, version bumped from 2.0.0 to 2.0.1, README release note stayed historical, and the Python test suite passed. |
|
@greptile please review this PR in the context of the related SDK/MCP sync PRs. Focus on release-path correctness, generated-code drift, and whether the centralized contract assumptions are robust. |
|
@greptile final re-review please in context of the roe-main release fan-out PR. Please focus on generated wrapper drift, README block sync, and whether this 2.0.0 bootstrap is ready to be regenerated by the roe-main prepare-target CLI on future releases. |
|
@greptile re-review latest commit please. Added Python SDK CI test/lint and widened codegen drift checks to include wrappers, README blocks, generated friendly API files, and README sync output. |
|
@greptile re-review latest head please. This is now 1.0.82 rather than 2.0.0; please focus on the Python SDK wrappers that MCP calls directly, idempotency header propagation, and generated wrapper drift. Prior Greptile was 5/5 but referenced an older commit; please update against the current head. |
Summary
1.0.802.openapi/wrappers.yml.Related PRs
Verification
uv run --locked ruff check .uv run --locked pytest