chore(zarr-metadata): build 0.4.0 changelog - #266
Closed
d-v-b wants to merge 1 commit into
Closed
Conversation
Consume the pending news fragments (the zarr-developers#4119 model layer's feature and removal notes, plus a new doc fragment for the standalone documentation site and justfile from zarr-developers#4208/zarr-developers#4210) into CHANGELOG.md via towncrier for the zarr_metadata-v0.4.0 release. Assisted-by: ClaudeCode:claude-fable-5
7 tasks
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
1 participant
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 🤖
Release prep for
zarr_metadata-v0.4.0: towncrier consumes the pending news fragments intoCHANGELOG.md.The 0.4.0 section covers:
zarr_metadata.modellayer from feat(zarr-metadata): Zarr metadata model layer zarr-developers/zarr-python#4119 (frozen-dataclass document models, strict loc-aware validators,UNSETsentinel, store-key (de)serialization, pydantic integration, and the*JSONtype renames)No version bump is needed anywhere — the version derives from the release tag via hatch-vcs.
After this merges (upstream)
Per the package README release process:
The tag fires the
zarr-metadata releaseworkflow (build, smoke test, PyPI via OIDC). Since this tag is the first to contain the docs setup, activating it on RTD (the^zarr_metadata-v.*automation rule) will also mint the site's first versioned build and create/en/stable/.Verified:
just checkgreen on the branch (tests, ruff, pyright, strict docs build); pre-commit passes.🤖 Generated with Claude Code