Record the v0.29.1 Zenodo version DOI - #34
Open
emircbngl wants to merge 1 commit into
Open
Conversation
Zenodo minted it when the GitHub Release was published, so it could not go in the release commit
itself. Read back from Zenodo rather than assumed:
concept record 20778997 redirects to record 22047655
version DOI 10.5281/zenodo.22047655
metadata version v0.29.1
publication_date 2026-08-21
https://doi.org/10.5281/zenodo.22047655 resolves (302 -> zenodo.org).
README needs no change: every DOI it cites is the CONCEPT DOI (badge, BibTeX, prose), which is
version-independent and always resolves to the latest release.
CITATION.cff still parses as YAML (24 identifiers, concept DOI first). check_release_consistency.py
PASS (pre mode, 0.29.1).
Co-Authored-By: Claude Opus 5 <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.
Follow-up to #33, as flagged there. Zenodo mints the version DOI when the GitHub Release is
published, so it could not go in the release commit.
Read back from Zenodo rather than assumed:
https://doi.org/10.5281/zenodo.22047655resolves (302 → zenodo.org).README needs no change. Every DOI it cites — the badge, the BibTeX block, the prose — is the
concept DOI, which is version-independent and always resolves to the latest release. Only
CITATION.cffcarries the per-version list.CITATION.cffstill parses as YAML (24 identifiers, concept DOI first, v0.29.1 above v0.29.0).tools/check_release_consistency.pyPASS (pre mode, 0.29.1).