Skip to content

Release 16.3.0: add agent conflict errors#190

Merged
gavinsharp merged 5 commits into
mainfrom
fern-bot/2026-06-18_18-07-55_773
Jun 18, 2026
Merged

Release 16.3.0: add agent conflict errors#190
gavinsharp merged 5 commits into
mainfrom
fern-bot/2026-06-18_18-07-55_773

Conversation

@fern-api

@fern-api fern-api Bot commented Jun 18, 2026

Copy link
Copy Markdown
Contributor

16.2.0 -> 16.3.0

Adds a typed 409 conflict error for concurrent agent chat turns and clarifies session concurrency docs. Also expands fhir2omop docs around supported resource mappings and dropped-resource semantics. Minor bump because the SDK adds a public typed error.

Added

  • phenoml.agent.errors.ConflictError — new ApiError subclass raised by client.agent.chat.send(...) and client.agent.chat.stream(...) for HTTP 409 responses when a session already has an active turn.

Changed

  • client.agent.chat.send(...) and client.agent.chat.stream(...) session_id parameter — docstring now states that only one request may be active per session at a time and overlapping turns return 409 Conflict.
  • client.fhir2omop.create(...) — docstring now lists the supported FHIR resource-to-OMOP table mappings and clarifies that unsupported resource types are accepted but ignored.
  • CreateOmopResponse.dropped — field description now clarifies that only supported resources missing required subject/patient, code, or medication reference data appear in dropped; unsupported resource types are ignored.

Note

Low Risk
Additive public error type and documentation-only fhir2omop clarifications; no runtime mapping logic changes in this diff.

Overview
Release 16.3.0 bumps the Fern-generated Python SDK and bundled OpenAPI spec to match the updated API.

Agent chat: Adds public ConflictError (phenoml.agent.errors) and maps HTTP 409 to it in sync/async send and stream raw clients. session_id docs now state one active turn per session; overlapping requests get 409.

FHIR2OMOP: Expands create docstrings and CreateOmopResponse.dropped field text to document FHIR→OMOP resource mappings, which types are ignored vs listed under dropped, and supported row-producing resource types.

Also updates changelog, reference docs, User-Agent/SDK version strings, Fern replay metadata, and minor lockfile bumps (anyio, certifi).

Reviewed by Cursor Bugbot for commit c49a9a4. Bugbot is set up for automated code reviews on this repo. Configure here.

fern-api Bot and others added 4 commits June 18, 2026 18:07
Generated by Fern
CLI Version: unknown
Generators:
  - fernapi/fern-python-sdk: 5.14.13
…ection and expand fhir2omop docs

Introduce a new ConflictError (HTTP 409) raised by the agent chat
endpoints when overlapping turns are submitted for the same session ID.
Also expand fhir2omop docstrings with a detailed FHIR-to-OMOP resource
mapping table and clarify the semantics of the `dropped` field.

Key changes:
- Add `phenoml.agent.errors.ConflictError` (ApiError subclass, status 409) and export it from `phenoml.agent`
- Raise `ConflictError` in all four chat client variants (sync/async, raw/high-level) when the server returns 409
- Update `session_id` docstring to document the one-active-request-per-session constraint
- Expand `client.fhir2omop.create()` docstring with a full FHIR resource → OMOP table mapping and unsupported-resource behaviour
- Clarify `CreateOmopResponse.dropped` field description: only supported resource types with missing required data appear here

🌿 Generated with Fern
Patches applied (1):
  - patch-6516695e: Release 15.0.2: restore bundled openapi.json packaging (#169)
@gavinsharp gavinsharp changed the title feat: add ConflictError for concurrent session detection and expand fhir2omop docs Release 16.3.0: add agent conflict errors Jun 18, 2026
@gavinsharp gavinsharp merged commit 4703090 into main Jun 18, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant