Release v1.9.1

[alex-omophub]

Summary by cubic

Releases v1.9.1 with SDK updates to match the current API contract. Similarity search now defaults to semantic instead of hybrid, supports pagination and new filters, and autocomplete raises ResponseError instead of silently returning an empty list when the response shape changes.

Search API

• Similarity search returns pagination from the response envelope and supports page, concept_class_ids, exclude_self, and the semantic default algorithm; metadata now includes totals_are_lower_bound and degraded_from.
• Autocomplete accepts domain_ids with domains kept as a deprecated alias, models the seven-field suggestion entries, and still accepts the older bare-list response shape.
• Added ResponseError so an unreadable autocomplete payload is distinguishable from a legitimate empty result.

Mappings

• Mappings.map() and AsyncMappings.map() now always send include_invalid explicitly, including its False default, and document the unmapped_sources and summary result fields.

Callers who relied on the previous hybrid default algorithm in similarity search will now get semantic results unless they pass algorithm explicitly.

^{Written for commit 1806df9. Summary will update on new commits.}

[codecov]

Codecov Report

❌ Patch coverage is 85.10638% with 14 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/omophub/resources/search.py	68.18%	7 Missing and 7 partials ⚠️

📢 Thoughts on this report? Let us know!

[cubic-dev-ai]

2 issues found across 12 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="src/omophub/_request.py">

<violation number="1" location="src/omophub/_request.py:178">
P3: The new public `post_raw` methods (sync and async) have no unit tests, while the parallel `get_raw` methods have full coverage (success, params, error, rate-limit, invalid-JSON) and `post` has its own test. `post_raw` is now a dependency of `resources/search.py` pagination, so a regression in raw-response handling would go undetected. Add sync and async `post_raw` tests mirroring the `get_raw`/`post` cases.</violation>
</file>

<file name="README.md">

<violation number="1" location="README.md:70">
P3: The README example indexes `mapped["summary"]`, but the repo's own example for the same `client.mappings.map()` method (`examples/map_between_vocabularies.py`) reads `result.get("mapping_summary", {})`. `map()` returns the raw API `data` unmodified, so only one key name is correct; if the API field is `mapping_summary`, the README's `mapped["summary"]` raises a KeyError. Align the README with the actual response key (or confirm which is right and fix the other).</violation>
</file>

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: The new public post_raw methods (sync and async) have no unit tests, while the parallel get_raw methods have full coverage (success, params, error, rate-limit, invalid-JSON) and post has its own test. post_raw is now a dependency of resources/search.py pagination, so a regression in raw-response handling would go undetected. Add sync and async post_raw tests mirroring the get_raw/post cases.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At src/omophub/_request.py, line 178:

<comment>The new public `post_raw` methods (sync and async) have no unit tests, while the parallel `get_raw` methods have full coverage (success, params, error, rate-limit, invalid-JSON) and `post` has its own test. `post_raw` is now a dependency of `resources/search.py` pagination, so a regression in raw-response handling would go undetected. Add sync and async `post_raw` tests mirroring the `get_raw`/`post` cases.</comment>

<file context>
@@ -175,6 +175,29 @@ def post(
         )
         return self._parse_response(content, status_code, headers)
 
+    def post_raw(
+        self,
+        path: str,
</file context>

[cubic-dev-ai]

P3: The README example indexes mapped["summary"], but the repo's own example for the same client.mappings.map() method (examples/map_between_vocabularies.py) reads result.get("mapping_summary", {}). map() returns the raw API data unmodified, so only one key name is correct; if the API field is mapping_summary, the README's mapped["summary"] raises a KeyError. Align the README with the actual response key (or confirm which is right and fix the other).

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At README.md, line 70:

<comment>The README example indexes `mapped["summary"]`, but the repo's own example for the same `client.mappings.map()` method (`examples/map_between_vocabularies.py`) reads `result.get("mapping_summary", {})`. `map()` returns the raw API `data` unmodified, so only one key name is correct; if the API field is `mapping_summary`, the README's `mapped["summary"]` raises a KeyError. Align the README with the actual response key (or confirm which is right and fix the other).</comment>

<file context>
@@ -61,6 +61,15 @@ for c in results["concepts"]:
+    "SNOMED",
+    source_codes=[{"vocabulary_id": "ICD10CM", "concept_code": "E11.9"}],
+)
+print(mapped["summary"])
+print(mapped["unmapped_sources"])
+
</file context>

Suggested change

	print(mapped["summary"])
	print(mapped["unmapped_sources"])
	print(mapped["mapping_summary"])
	print(mapped["unmapped_sources"])