Repository navigation
Release 0.2.2 (docs/metadata + Zenodo DOI bootstrap) - #27
Merged
Merged
Conversation
One-off maintenance release (outside the normal milestone/urgent-fix cadence) to bootstrap Zenodo archival — the project's first software DOI — and to ship the documentation/metadata accumulated since 0.2.1 (CITATION.cff, README badges, AGENTS.md/CLAUDE.md, RELEASING.md, .zenodo.json) plus the dead-code removal of the two broken alternate entry points. No functional code change; golden master unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Version bump
0.2.1 → 0.2.2+ CHANGELOG, to cut the 0.2.2 release.Why
A one-off maintenance release, deliberately outside RELEASING.md's normal "milestone or urgent fix" cadence, to:
.zenodo.jsonis in place.No functional code change; the numerical core / golden master is unchanged. The one-off rationale is recorded in the CHANGELOG, not in RELEASING.md — a single event doesn't belong in the standing policy.
After merge
Per RELEASING.md: create GitHub Release
v0.2.2targetingmain→publish.ymluploads to PyPI and Zenodo archives the release and mints the DOI. Then the Zenodo DOI badge goes on the README and adoi:field on CITATION.cff.🤖 Generated with Claude Code