Repository navigation
Record the v0.2.0 release - #3
Merged
Merged
Conversation
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.
Marks the v0.2.0 entry in RELEASE.md done and records how it was released: the tag on the merge commit, both distributions built from the tag's tree and on PyPI, Zenodo record 23005806 published and read back anonymously, the version DOI registered, and the docs redeployed. It also records that the Zenodo draft could not be read as rendered with an API token, what was read instead, and that the record's dates say 2026-09-27 while the publish fell on 2026-09-28. RELEASE.md only; no code, vectors or docs chapters change.