CITATION.cff version is not checked or updated at release
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Read the existing CHANGELOG version check in .goreleaser.yaml, .github/scripts/release-notes.sh, and the release job in .github/workflows/go.yml; also review the release checklist in CONTRIBUTING. Add a release-time check that compares the CITATION.cff version with the tag, and document the check in the checklist. Done means a release fails when the versions differ.
Written by the indexing model from the issue text.
Description
Why it matters
CITATION.cff (#75) is what GitHub's "Cite this repository" button and reference managers read. Its version and date-released are hard-coded, so after the next release every citation will name an outdated version.
Evidence
CITATION.cffhasversion: 0.8.0anddate-released: "2026-10-04".- The release pipeline (
.goreleaser.yaml,.github/scripts/release-notes.sh, thereleasejob in.github/workflows/go.yml) checksCHANGELOG.mdfor the version's section but never reads or updatesCITATION.cff.
Suggested approach
Add a release-time check that fails the release when CITATION.cff's version does not match the tag, next to the existing CHANGELOG check. Add a line to the release checklist in CONTRIBUTING. Alternatively, have the release job rewrite both fields, but a check is simpler and keeps the file reviewed in a PR.
Done when
A release cannot be tagged while CITATION.cff names a different version.
- Dominant language
- Go
- Stars
- 1
- Forks
- 1
- Avg merge
- 14d 9h
- Merged PRs (30d)
- 1
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TMHSDigital/subenum
-
documentation testing
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
TMHSDigital/subenum#103 ·
Maintainers usually reply within 1 day
-
community marketing priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#132 ·
Maintainers usually reply within 1 day
-
feature priority: low
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#131 ·
Maintainers usually reply within 1 day
-
documentation marketing priority: medium
Difficulty 5/5 Over a week Newbie friendliness 25/100
TMHSDigital/subenum#127 ·
Maintainers usually reply within 1 day
-
ci feature marketing priority: medium
Difficulty 5/5 Over a week Newbie friendliness 35/100
TMHSDigital/subenum#126 · 1 comment ·
Maintainers usually reply within 1 day
All issues in TMHSDigital/subenum
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
golang/go#82033 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
FootprintAI/Containarium#2338 ·
Maintainers usually reply within 1 day
-
[Bug]: core doesn't build standalone on dev since a17068054 (go-mp3 require dropped, go.sum pruned)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
SagerNet/sing-openvpn#11 ·
-
priority: P3 type: devops
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
jiegui2025/hwspec#57 ·
Maintainers usually reply within 1 day