fix: Zenodo + CITATION metadata — bump to v0.3.1, add date-released#28
Open
Zer0pa-Architect-Prime wants to merge 2 commits into
Open
fix: Zenodo + CITATION metadata — bump to v0.3.1, add date-released#28Zer0pa-Architect-Prime wants to merge 2 commits into
Zer0pa-Architect-Prime wants to merge 2 commits into
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
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
Zenodo/citation metadata hygiene for the v0.3.1 release (PyPI live since 2026-04-25).
CITATION.cffversion: 0.3.0 → 0.3.1; adddate-released: "2026-04-25".zenodo.json"version": "0.3.1"fieldWhy
CITATION.cffwas not bumped when v0.3.1 shipped to PyPI; Zenodo auto-capture and academic citation tools would have cited the wrong version..zenodo.jsonhad noversionfield; Zenodo would infer it from the tag name but explicit is safer.Checks
LicenseRef-Zer0pa-SAL-7.0).Remaining open items (operator decision needed, not in this PR)
## Provenancesection absent from README (§3.3 compliance gap).commit_shain README## Repo Identityis stale (c5e8bf11a1c1vs live HEAD).