Found while reviewing #4, which publishes v0.1.0 as "the first citable baseline".
CITATION.cff has no version: and no date-released: key. The only version-shaped field in it is cff-version: 1.2.0, which is the CFF format version, not the software version.
The maintainer release checklist in CONTRIBUTING.md bumps package.json and regenerates CHANGELOG.md, but nothing updates the citation metadata — so anyone citing TextRefs from CITATION.cff, and the Zenodo deposit that reads it, gets a record with no version string and no release date.
For a project whose entire subject is citable, persistent identity, that is a conspicuous gap.
Fix:
- add
version: 0.1.0 and date-released: <tag date> to CITATION.cff
- add both to the release checklist alongside the
package.json bump, so they cannot drift again
Related: the checklist step 7 ("fill the concept DOI into CITATION.cff identifiers:") already anticipates touching this file after the first release — the identifiers: block is currently commented out.
Found while reviewing #4, which publishes v0.1.0 as "the first citable baseline".
CITATION.cffhas noversion:and nodate-released:key. The only version-shaped field in it iscff-version: 1.2.0, which is the CFF format version, not the software version.The maintainer release checklist in
CONTRIBUTING.mdbumpspackage.jsonand regeneratesCHANGELOG.md, but nothing updates the citation metadata — so anyone citing TextRefs fromCITATION.cff, and the Zenodo deposit that reads it, gets a record with no version string and no release date.For a project whose entire subject is citable, persistent identity, that is a conspicuous gap.
Fix:
version: 0.1.0anddate-released: <tag date>toCITATION.cffpackage.jsonbump, so they cannot drift againRelated: the checklist step 7 ("fill the concept DOI into
CITATION.cffidentifiers:") already anticipates touching this file after the first release — theidentifiers:block is currently commented out.