From 6cdfddf458ba7abed797b9a4a5b622e709ca4389 Mon Sep 17 00:00:00 2001 From: amarcozzi Date: Wed, 15 Jul 2026 12:10:44 -0600 Subject: [PATCH] Require zarr>=3 so environments can open v2 API exports The SDK never imports zarr; the dependency exists so that a user's environment can open the zipped-Zarr grid exports the API hands out via signed download URLs. Those exports are Zarr format v3, and zarr-python 2.x cannot read v3 at all, so an unpinned `zarr` that resolves to 2.x leaves the user unable to open an export the SDK just downloaded for them. This mainly affects v1 migrants: v1 pinned zarr==2.18.2 and handed out format v2, so an environment carried over from v1 can be on a zarr that silently cannot read v2 exports. Refs silvxlabs/FastFuels-API-v2#447 --- pyproject.toml | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index 210557f..b1f79ae 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -28,7 +28,10 @@ dependencies = [ "requests", "scipy", "urllib3>=2.1.0", - "zarr", + # Not imported by the SDK: present so environments can open the API's + # zipped-Zarr grid exports, which are written as format v3. zarr-python + # 2.x cannot read v3 at all. + "zarr>=3", ] [project.urls]