build(deps): bump idc-index 0.13.1 -> 0.13.3 (idc-index-data 25.0.4)

CHANGELOG.md

@@ -20,6 +20,24 @@ Refactors, CI, and formatting land in the git history, not here.
   escape a value it did not author — an identifier taken from a URL, a name a user typed — and
   such a value can no longer change the shape of the query.
 
+### Changed
+
+- **`idc-index` 0.13.3 / `idc-index-data` 25.0.4** (still IDC v25): a missing value in
+  `index.PatientAge`, `index.SeriesDescription`, `pt_index.SeriesType`,
+  `collections_index.supporting_data` or `clinical_index.column_label` is now NULL, never an empty
+  string, so SQL that tested `= ''` must test `IS NULL`. `volume_geometry_index` adds
+  `origin_patient`, `ImageOrientationPatient` and `slice_spacing_mm`. `GET /v3/version` and
+  `get_idc_version` report `idc_index_data_version` `25.0.4`; collection, series, and size totals
+  are unchanged.
+
+### Fixed
+
+- `get_table_schema` and `list_attributes` describe 19 columns that had no description, among
+  them `SeriesInstanceUID` in `index`, `sm_index` and `ann_index`, and `Rows`/`Columns` in
+  `ct_index`, `mr_index` and `pt_index`. `analysis_result_id` is described as NULL for original
+  data rather than as "not empty", and `seg_index.segmented_SeriesInstanceUID` says when it is
+  NULL.
+
 ## [3.0.0b6] — 2026-10-15
 
 Beta iteration: picks up the `idc-index-data` 25.0.1 patch, so `seg_index` covers Label Map

dev/deployment.md

@@ -160,7 +160,7 @@ python3 dev/smoke_openapi_examples.py "$URL"
 The image installs dependencies from [uv.lock](../uv.lock) (see [Dockerfile](../Dockerfile)), so
 it bakes exactly the `idc-index-data` the lock records and a rebuild of the same commit is
 deterministic. To move IDC versions, bump the exact `idc-index` pin in
-[pyproject.toml](../pyproject.toml) (e.g. `idc-index==0.13.1`, which pulls a specific
+[pyproject.toml](../pyproject.toml) (e.g. `idc-index==0.13.3`, which pulls a specific
 `idc-index-data`), run `uv lock` and commit both files — CI's `uv sync --locked` fails if the lock
 is stale — then **rebuild and redeploy** (steps 2–3). The running version is always reported at
 `/v3/version`.

pyproject.toml

@@ -11,12 +11,12 @@ keywords = ["IDC", "DICOM", "cancer imaging", "MCP", "REST", "idc-index"]
 dependencies = [
     # Query engine + data.
     # idc-index is pinned EXACTLY, unlike every other dependency here, because it transitively
-    # pins idc-index-data (0.13.1 -> 25.0.1) — which *is* the IDC data release this server
+    # pins idc-index-data (0.13.3 -> 25.0.4) — which *is* the IDC data release this server
     # advertises at /v3/version and documents in the changelog. The image installs from uv.lock,
     # so the lock alone already fixes it; the exact pin keeps the served IDC release explicit
     # here and stops a routine `uv lock --upgrade` from silently moving it. Bump this pin (then
     # `uv lock`) to move IDC versions — see dev/deployment.md § Updating for a new IDC release.
-    "idc-index==0.13.1",
+    "idc-index==0.13.3",
     "duckdb>=1.5.5",
     "pyarrow>=25.0.0",
     # Shared models / settings

src/idc_api/rest/app.py

@@ -385,7 +385,7 @@ def health():
                                 "summary": "Illustrative — not live values",
                                 "value": {
                                     "idc_version": "v25",
-                                    "idc_index_data_version": "25.0.1",
+                                    "idc_index_data_version": "25.0.4",
                                     "api_version": "3.0.0",
                                     "build": "a1b2c3d",
                                 },