Repository navigation
docs: release notes for 0.17.0 - #859
Merged
Merged
Conversation
Restructure the Unreleased section into a 0.17.0 release section with Breaking changes / Deprecations / Maintenance headings. - Add missing entries for the Python 3.12 / NumPy 2.0 minimums (zarr-developers#834) and the pcodec 1.x update (zarr-developers#817), neither of which was documented. - Move the tests relocation (zarr-developers#829) and the removal of DISABLE_NUMCODECS_CEXT (zarr-developers#826) from Maintenance to Breaking changes, and note that tests are still shipped in the sdist. - Document the delta_spec="none" -> "no_op" deprecation (zarr-developers#817). - Fix leftover RST roles (:user:/:issue:) from the Markdown conversion, which do not render under MyST, and convert RST literal blocks to fenced code. - Add entries for the remaining maintenance PRs since v0.16.5. Assisted-by: ClaudeCode:claude-opus-5 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
d-v-b
force-pushed
the
docs/release-notes-0.17.0
branch
from
September 17, 2026 17:54
5d7e20f to
10c0a5b
Compare
d-v-b
marked this pull request as ready for review
September 17, 2026 17:56
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 AI text below 🤖
Prepares the release notes for 0.17.0. No code changes —
docs/release.mdonly.Why 0.17.0 and not 0.16.6
Per the versioning policy in
docs/contributing.md, micro releases are for "no changes to the public API", which doesn't hold here. Strictly read, that policy calls for a major bump on backwards-incompatible changes, but the project has never behaved that way — #622 dropped Python 3.10 / NumPy 1.23 in 0.14.0 under Maintenance, and 0.13.1 shipped a documented breaking change in a patch. De facto, breaking changes land in minors while we're on 0.x.The Python/NumPy drop alone would be weak grounds by that precedent. What makes this a minor is the
numcodecs.testsremoval, the build-system migration, and the free-threading work in #858.What changed in the notes
DISABLE_NUMCODECS_CEXT(Migrate build system from setuptools to meson-python #826) were under Maintenance — the latter buried mid-paragraph in the meson entry. The twonumcodecs.bloscbehavioral changes from Add free-threaded CPython (3.14t) support #858 (removal ofget_mutex, and thesem_openfallback change) moved out of Enhancements, with the free-threading support itself staying there and the two entries cross-referencing each other.tests/andfixture/are still in the sdist — confirmed by building one locally withmesonpy.build_sdist(all 40 test files present, andpyproject.tomlcarriestestpaths = ["tests"]). So distro packagers are unaffected; the break only hits code doingimport numcodecs.tests.commonat runtime. Worth stating explicitly, since "tests were removed" reads much scarier than it is.delta_specdeprecation from update pcodec #817 ("none"→"no_op", still works, now warns).:user:and:issue:, which don't render under MyST — collateral from the RST→Markdown conversion in Convert RST docs to markdown #830. Also converted an RST::literal block to a fenced code block.Follows the convention from #804: the new version section goes below an empty
Unreleasedheading.Note for a follow-up
.github/labeler.ymlstill matches on!docs/release.rst, but #830 renamed that file todocs/release.md. Sincerelease.rstcan no longer match, theneeds release noteslabel now fires on every PR unconditionally. Not fixed here to keep this PR to release notes — happy to send a one-liner separately.🤖 Generated with Claude Code