[test-bot] pip install --pre is failing

[github-actions]

The Test pre-releases workflow failed on 2025-11-30 01:54 UTC

The most recent failing test was on windows-latest py py311
with commit: 88fca83

Full run: https://github.com/ome/ome-zarr-py/actions/runs/19792161972

(This post will be updated if another test fails, as long as this issue remains open.)

[will-moore]

@joshmoore I think this is the same error as fixed in #488 (now merged).

        img_path = str(self.path / "test_read_v05.zarr")
>       root = zarr.group(img_path)
               ^^^^^^^^^^^^^^^^^^^^

Don't know if we need to release that (fix is just in the test itself) but #487 looks like it would be useful to release

[jdblischak]

Don't know if we need to release that (fix is just in the test itself) but #487 looks like it would be useful to release

Just to add the context from conda-forge. On our end there is no rush to release the removal of the v from the zarr lower bound (ie #487). I've already updated the conda-forge recipe (conda-forge/ome-zarr-feedstock#31) and repodata (conda-forge/conda-forge-repodata-patches-feedstock#1068), so that is all working fine. And for anyone using pip (or one of its many wrappers), the version string v3.0.0 is fine.

The main benefit would be for other downstream packaging efforts. I just looked at Nix, and their recipe for ome-zarr doesn't even have any version constraints (not sure how that works, but I am not a Nix expert).