Repository navigation
Release Zarr-Python v3.4.0 #4256
Copy link
Copy link
Closed
Description
Release: v3.4.0 (originally planned as v3.3.1; renamed because main now carries two features — #4063 adds a required msgspec dependency and stricter metadata parsing, and #4277 changes the exception types raised for unknown codecs)
Scheduled Date: 2026/08/13
Priority PRs/issues to complete prior to release
- "ValueError: Input array must be contiguous" when *cast_value* codec next to *transpose* codec #4237
- fix(chunk-grids): make array creation O(1) in per-dimension chunk count #4218
- The roadmap: docs: add roadmap page outlining future plans #4149
- Add unified JSON metadata validation via msgspec (#3285) #4063
Before release:
- Check SPEC 0 to see if the minimum supported version of Python or NumPy needs bumping.
- Verify that the latest CI workflows on
mainare passing: Tests, GPU Tests, Hypothesis, Docs, Lint, Wheels. - Run the downstream tests against
main(passed 2026-09-09: https://github.com/zarr-developers/zarr-python/actions/runs/34338567820; re-run on3203018cafter 12 more merges: https://github.com/zarr-developers/zarr-python/actions/runs/34414991933): go to the workflow page, click "Run workflow", and select themainbranch. Verify that the Xarray and numcodecs integration tests pass. - Open a release PR with the changelog entries for the upcoming release (docs: 3.4.0 release notes #4360, draft), generated with
uv run --only-group release towncrier build --version x.y.z. - Review the release PR and verify the changelog in
docs/release-notes.mdlooks correct. - Merge the release PR.
Release:
- Draft a new GitHub Release with tag
vX.Y.Ztargetingmain. Use "Generate release notes" for the description. - Verify the release is published on PyPI and ReadTheDocs.
After release:
- Review and merge the pull request on the conda-forge zarr-feedstock that will be automatically generated. Note: this release adds
msgspec>=0.19as a required dependency, so the recipe needs a manual edit.
- Party 🎉
Releasing from a branch other than main
In rare cases (e.g. patch releases for an older minor version), you may need to release from a dedicated release branch (e.g. 3.1.x):
- Create the release branch from the appropriate tag if it doesn't already exist.
- Cherry-pick or backport the necessary commits onto the branch.
- Run
towncrier build --version x.y.zand open the release PR against the release branch instead ofmain. - Run the downstream tests against the release branch instead of
main. - When drafting the GitHub Release, set the target to the release branch instead of
main. - After the release, ensure any relevant changelog updates are also reflected on
main.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels
Activity
d-v-b commentedon Aug 16, 2026
I'd like to move forward on this release autonomously on monday, please let me know if there's any reason not to proceed!
[-]Release Zarr-Python v3.3.1[/-][+]Release Zarr-Python v3.4.0[/+]d-v-b commentedon Sep 16, 2026
closed by the release of 3.4.0