[roeai-release-bot]

This PR updates the Python SDK for release 1.1.22.

Generated from:

• roe-main release branch 1-1-5
• roe-main commit f0c6dd519d94649cd2984d45d64faed60e99527e

[greptile-apps]

Confidence Score: 4/5

[Medium impact] The changes affect connection management and agent job-list workflows.

Fix the generated response schema before merging so connection updates can return the new confirmation conflict without crashing.

Findings

1.  Confirmation conflicts fail to load ▶
2.  Friendly methods miss lifecycle options ▶

Summary

Releases the SDK as 1.1.22 with connection lifecycle fields and confirmation support.

• Connection lists and records now carry lifecycle states.
• Connection updates can ask for confirmation when agents or webhooks use them.
• Job lists now identify the agent version that ran each job.
• The SDK package and release notes now say 1.1.22.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Update connection] --> B{Call path}
    B --> C[Friendly method]
    B --> D[Generated endpoint]
    C --> E[Server returns in-use conflict]
    D --> F[Server returns in-use conflict]
    E --> G[SDK exception preserves error body]
    F --> H[DuplicateConnectionResponse requires existing_connection]
    H --> I[KeyError]

Loading

_{Reviews (1) · Last reviewed commit: "Release v1.1.22" · Reviewed by Greptile}

[greptile-apps]

Confirmation conflicts fail to load

The new in-use conflict returns {error, in_use: true}, but both PUT and PATCH still read every 409 as DuplicateConnectionResponse. That model requires existing_connection, which this response lacks. Callers using the generated endpoints with client.raw get KeyError instead of the conflict, so they cannot inspect in_use before resending with confirm_in_use.

Describe both conflict shapes in the response schema and regenerate the models and endpoints.

Knowledge Base Used: Generated API integration

[greptile-apps]

Friendly methods miss lifecycle options

The new lifecycle filter and update field are missing from the friendly wrapper contract. client.connections.list(lifecycle="active") and client.connections.update(id, lifecycle="archived") reject the argument. Users must switch to generated endpoint calls to filter active connections or archive and reactivate them.

Add optional lifecycle arguments to list, update, and replace in the wrapper contract and regenerate the friendly methods.

Knowledge Base Used: Wrapper generation