Repository navigation
Release Zarr-Python v3.1.2 #3397
Copy link
Copy link
Closed
Description
Release: v3.1.2
Scheduled Date: 2025/08/22
Priority PRs/issues to complete prior to release
Before release:
- Make sure that all pull requests which will be included in the release have been properly documented as changelog files in the
changes/directory. - Run
towncrier build --version x.y.zto create the changelog, and commit the result to the release branch. - Check SPEC 0 to see if the minimum supported version of Python or NumPy needs bumping.
- Check to ensure that:
- Deprecated workarounds/codes/tests are removed. Run
grep "# TODO" **/*.pyto find all potential TODOs. - All tests pass in the "Tests" workflow.
- All tests pass in the "GPU Tests" workflow.
- All tests pass in the "Hypothesis" workflow.
- Check that downstream libraries work well (maintainers can make executive decisions about whether all checks are required for this release).
- numcodecs
- Xarray (@jhamman @dcherian @TomNicholas)
- Zarr's upstream compatibility is tested via the Upstream Dev CI worklow.
- Click on the most recent workflow and check that the
upstream-devjob has run and passed.upstream-devis not run on all all workflow runs. - Check that the expected version of Zarr-Python was tested using the
Version Infostep of theupstream-devjob. - If testing on a branch other than
mainis needed, open a PR modifying https://github.com/pydata/xarray/blob/90ee30943aedba66a37856b2332a41264e288c20/ci/install-upstream-wheels.sh#L56 and add therun-upstreamlabel.
- Titiler.Xarray (@maxrjones)
- Modify dependencies for titiler.xarray.
- Modify triggers for running the test workflow.
- Push the branch to the repository and check for the actions for any failures.
- Deprecated workarounds/codes/tests are removed. Run
Release:
- Go to https://github.com/zarr-developers/zarr-python/releases.
- Click "Draft a new release".
- Choose a version number prefixed with a
v(e.g.v0.0.0). For pre-releases, include the appropriate suffix (e.g.v0.0.0a1orv0.0.0rc2). - Set the target branch to the release branch (e.g.,
3.1.x) - Set the description of the release to:
See release notes https://zarr.readthedocs.io/en/stable/release-notes.html#release-0-0-0, replacing the correct version numbers. For pre-release versions, the URL should omit the pre-release suffix, e.g. "a1" or "rc1". - Click on "Generate release notes" to auto-fill the description.
- Make a release by clicking the 'Publish Release' button, this will automatically create a tag too.
- Verify that release workflows succeeded.
- The latest version is correct on PyPI.
- The stable version is correct on ReadTheDocs.
After release:
- Review and merge the pull request on the conda-forge zarr-feedstock that will be automatically generated.
- Party 🎉
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
[-]Release Zarr-Python v3.1.1[/-][+]Release Zarr-Python v3.1.2[/+]dcherian commentedon Aug 22, 2025
Xarray is seeing a regression in nightly tests: pydata/xarray#10640 cc @ianhi
d-v-b commentedon Aug 22, 2025
maybe a side effect of #3378?
ianhi commentedon Aug 22, 2025
Xarray was testing for the broken behavior with write_empty and append. I've updated the xarray test to account for this and everything passes locally: pydata/xarray#10665
ianhi commentedon Aug 22, 2025
QUick sidenote for xarray people probably @dcherian and @TomNicholas . To automate the upstream run check, and to confirm that the versions are good and that the workflow ran after the most recent commit to zarr main you can run this gist https://gist.github.com/ianhi/c21e4389f6a5ab71db92d92af92b4bd9
with
uv run https://gist.githubusercontent.com/ianhi/c21e4389f6a5ab71db92d92af92b4bd9/raw/3a95dfa58ee462b97c76b8f6383420b47b7effe0/zarr_upstream_checker.pygiving:
d-v-b commentedon Aug 25, 2025
see #3404 for a PR with the release notes, after we get that in I think we are ready to go
dcherian commentedon Aug 25, 2025
Thanks @ianhi ; I think we should add that gist to this repository
dstansby commentedon Aug 26, 2025
A quick note that #3406 should block the release (because it's a new bug, uncovered/surfaced by #3307 which has not yet been released)
d-v-b commentedon Aug 26, 2025
should have blocked, perhaps -- we released 3.1.2 yesterday. But once this bug is fixed we can issue 3.1.3