Release v1.1.7

[roeai-release-bot]

This PR updates the Python SDK for release 1.1.7.

Generated from:

• roe-main release branch 1-0-91
• roe-main commit 52d983a0c8ce72b6704d039d0b089f386a02a6e8

[greptile-apps]

Greptile Summary

This release adds connection-list ordering, exposes credential-configuration state on connection models, and updates the SDK release metadata. Two issues need correction before merging: the focused create, update, and replace transport tests fail because their shared response fixture omits the newly required credentials_configured field, and the public ConnectionsAPI.list() method does not expose the new ordering option.

Validation reproduced all three response-parsing failures and confirmed that the generated endpoint sends ordering=name successfully while the public SDK method rejects the same argument before making a request.

Confidence Score: 3/5

Not safe to merge until the broken connection-response test fixtures and missing public ordering parameter are corrected.

Two independent user-visible problems were reproduced: three core connection mutation test paths fail while parsing their response fixture, and the newly added ordering capability is inaccessible through the public SDK facade.

Files Needing Attention: tests/unit/test_connections_wrapper_transport.py needs its shared response fixture updated; src/roe/api/connections.py needs to accept and forward ordering. src/roe/_generated/models/connection.py defines the required field that triggers the fixture parsing failure.

T-Rex Logs

What T-Rex did

• Reviewed a posted P1 finding that reports focused connection wrapper test failures when credentials_configured is absent, supported by the focused connection wrapper test log.
• Inspected the focused public connections ordering contract check source and the runtime output showing the rejected ordering argument and the generated ordered request.
• Validated another P1 finding with no artifacts attached.
• Reviewed the general-contract-validation-proof, noting that pytest traces show KeyError on missing credentials_configured in _connection_json.
• Compared public ordering contract behavior end-to-end, observing that facade.list(ordering='name') errors before a request is sent while the internal sync_detailed call returns 200 OK with an ordering parameter; this was informed by the review script and runtime output artifacts.

_{Ran code and verified through T-Rex}

Comments Outside Diff (3)

1. src/roe/api/connections.py, line 43-59 (link)

   Connections facade drops ordering support

   ConnectionsAPI.list() neither accepts nor forwards ordering, although the generated connections-list operation supports it in the query string. Calling the public SDK method with ordering="name" raises TypeError before a request is issued, so users cannot use the newly added ordering feature without bypassing the supported facade. Add the argument and forward it as UNSET when omitted.

   Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

   Artifacts

   
   

   Focused public connections ordering contract check source

   • Review-authored executable script that invokes the public facade with ordering and captures the generated endpoint request contract; it is the runnable reproduction.

   Runtime output for rejected public ordering argument and generated ordered request

   • Captured output from the focused check shows the public call's TypeError before dispatch and the generated endpoint's 200 OK request containing ordering=name; the contract bug is confirmed.

   

   _{Ran code and verified through T-Rex}

   

2. General comment

   Connection wrapper operations reject responses without credentials_configured

   • Bug
     • The create, update, and replace wrapper tests all fail before their transport assertions can complete when parsing the fixture response. The exact observed exception is KeyError: 'credentials_configured' at src/roe/_generated/models/connection.py:172; pytest reports 3 failed tests and exit code 1.
   • Cause
     • Connection.from_dict unconditionally executes d.pop("credentials_configured"), while the focused test fixture _connection_json() omits that key.
   • Fix
     • Make generated response parsing tolerate the absent field if the API contract permits omission (for example, use an appropriate default/optional field), or ensure every API response and test fixture supplies credentials_configured if it is required by contract.

   _{Ran code and verified through T-Rex}

3. General comment

   Connections public facade omits generated ordering parameter

   • Bug
     • The public ConnectionsAPI.list() signature does not accept ordering. Calling it with ordering="name" raises TypeError before an HTTP request is made, even though the underlying generated endpoint accepts the parameter and serializes it into the query string.
   • Cause
     • src/roe/api/connections.py defines and forwards only connector_type, search, page, and page_size; it omits ordering that is present in src/roe/_generated/api/connections/connections_list.py.
   • Fix
     • Add ordering: str | None = None to ConnectionsAPI.list() and forward ordering=ordering if ordering is not None else UNSET to request_raw. Regenerate the friendly facade from its wrapper specification if it is generated.

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "Release v1.1.7" | Re-trigger Greptile}

[greptile-apps]

Connection response fixture omits credential state

Connection.from_dict() now requires credentials_configured, but the shared _connection_json() fixture used by the create, update, and replace transport tests does not provide it. Each response is therefore rejected with KeyError before its transport assertions complete. Update the fixture to include the required response field so these regression tests pass against the new model contract.

Artifacts

Focused connection wrapper test failures when credentials_configured is absent

• Ran the requested uv pytest command against the existing fixture; it captures three KeyError failures at the unconditional credentials_configured pop, confirming the bug.

_{Ran code and verified through T-Rex}