0.8.0: scouts.update(is_public), APIConnectionError for transport failures, lazy chat namespace

[dhruvbatra]

Changes

scouts.update(is_public=...) — the developer API's PATCH already accepts is_public, but neither client exposed it on update() (only create()), so visibility couldn't be changed after creation through the SDK; yutori-mcp's edit_scout hit a TypeError. Added to both sync and async namespaces through the shared payload builder. Verified live against production: an is_public edit round-trips correctly.

APIConnectionError for transport failures — handle_response already wraps auth failures, redirects, status errors, and non-JSON bodies, but httpx transport errors (timeouts, DNS/connect failures) escaped _request raw — and some (e.g. ReadTimeout) stringify to "", giving callers a blank error. Both _request chokepoints now raise APIConnectionError with a message that always names the underlying httpx exception type. Exported from the package root.

Lazy chat namespace — the chat namespace eagerly built an OpenAI client (its own HTTP client + SSL context) in every client __init__ — measured at roughly half the construction cost — even for callers that never use chat completions (yutori-mcp builds a client per tool call). Now constructed on first attribute access; close() releases it inside try/finally so an HTTP-client close failure can't leak it.

Version → 0.8.0.

Tests

442 passed, 3 skipped. New coverage: is_public wire payload (sync + async, including False surviving the None-filter), status mutual-exclusion with is_public, transport-error wrapping (sync + async, including blank-stringifying timeout), lazy-chat construction and close-without-use.

Release ordering

yutori-mcp pins yutori>=0.8.0 and consumes all three changes (is_public edit, APIConnectionError mapping, per-call client cost). Sequence: deploy yutori-ai/yutori#10031 → publish this as 0.8.0 → release yutori-mcp.

🤖 Generated with Claude Code

---

Note

Low Risk
Additive SDK API and error-type changes with tests; no auth or server logic changes, though callers may need to catch APIConnectionError for network failures.

Overview
Release 0.8.0 bumps package and installer version strings; API docs now list is_public on scouts.update.

Scout visibility: Sync and async scouts.update() accept is_public, wired through the shared payload builder so PATCH can change public/private after create (including False, which is not dropped as None). Combining status with is_public still raises the existing mutual-exclusion ValueError.

Transport errors: Shared sync/async _request paths catch httpx.HTTPError and raise exported APIConnectionError with a message that always includes the httpx exception type (avoids blank messages from errors like ReadTimeout("")).

Client lifecycle: YutoriClient / AsyncYutoriClient defer building the chat namespace (OpenAI client) until first access; close() uses try/finally so a built chat client is released even if the main HTTP client close fails.

^{Reviewed by Cursor Bugbot for commit ba91ec6. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit ba91ec6. Configure here.}

[cursor]

CLI misses APIConnectionError handler

Medium Severity

_request now raises APIConnectionError for transport failures instead of raw httpx errors. cli_api_errors still catches only httpx.HTTPError, so CLI commands using a real YutoriClient can show a Typer traceback on timeouts or connection failures instead of the intended friendly network message.

 

^{Reviewed by Cursor Bugbot for commit ba91ec6. Configure here.}