Zenodo fix 2#762
Merged
Merged
Conversation
… conversion The Zenodo integration was not merely disabled: the repository is enabled on Zenodo and the `release` webhook has been live since 2026-06-18, yet v2.4.0 (published 2026-07-04, a real non-draft release) shows as **failed** on Zenodo with no error detail, and the archive has been stuck at v1.57.1 since June 2025. That last successful archive is the final release before `CITATION.cff` was added on 2025-06-25, and nothing has archived since -- Zenodo derives its deposit from that file, and the conversion is lossy in at least two ways that can fail validation: CFF is required to spell the license with its SPDX identifier (`MIT`), whereas Zenodo's vocabulary only knows the lowercase `mit` (`GET /api/vocabularies/licenses/mit` -> 200, `.../MIT` -> 404), and the file also carries a `doi` plus a hand-pinned `version` that Zenodo is supposed to decide for itself. Rather than guess which field Zenodo chokes on, ship a `.zenodo.json`, which Zenodo reads in preference to `CITATION.cff` and ignores the CFF entirely: it pins no DOI and no version, so Zenodo mints the DOI and takes the version from the release tag, and it names the license in Zenodo's own vocabulary. `CITATION.cff` stays as the human- and GitHub-facing citation metadata, where SPDX `MIT` is correct. NOTE: This is the leading hypothesis, not a verified fix -- Zenodo reports the failure with no diagnostics, so it must be confirmed against Zenodo Sandbox before the next real release.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Continuation of #761