release: v0.5.1

CHANGELOG.md

@@ -6,6 +6,24 @@ to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [0.5.1] - 2026-07-28
+
+### Added
+
+- `CITATION.cff` now carries an ORCID and is validated against the CFF 1.2.0 schema, so
+  GitHub renders a **Cite this repository** panel and Zenodo can mint a DOI from it.
+- `.zenodo.json` pins the metadata Zenodo uses for the DOI record (title, description,
+  creators, licence, keywords) rather than letting it infer them from the repository.
+
+### Fixed
+
+- `CITATION.cff` claimed `0.4.0` while the project shipped `0.5.0`. Citation metadata is
+  machine-readable and ends up in other people's bibliographies, so a stale version there
+  is worse than none.
+- A new `citation` CI job fails any change where `CITATION.cff`'s version disagrees with
+  `pyproject.toml`, which is how the drift above went unnoticed. It mirrors the existing
+  "tag matches pyproject version" release gate, one layer earlier.
+
 ## [0.5.0] - 2026-07-03
 
 ### Added

CITATION.cff

@@ -15,8 +15,8 @@ authors:
 repository-code: "https://github.com/musharna/ghostcite"
 url: "https://pypi.org/project/ghostcite/"
 license: MIT
-version: 0.5.0
-date-released: "2026-07-03"
+version: 0.5.1
+date-released: "2026-07-28"
 keywords:
   - citations
   - crossref

pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "ghostcite"
-version = "0.5.0"
+version = "0.5.1"
 description = "Catch ghost citations — cross-check a bibliography's claimed author/year against CrossRef"
 readme = "README.md"
 requires-python = ">=3.9"

src/ghostcite/__init__.py

@@ -2,7 +2,7 @@
 
 from __future__ import annotations
 
-__version__ = "0.5.0"
+__version__ = "0.5.1"
 
 from ghostcite.api import CheckResult, check_claim_support, check_doi, check_text
 from ghostcite.models import (