Update Zenodo entry upon release - #345
Conversation
|
@rkdarst you were interested in the automation of the Zenodo deposit. Would you like to test this implementation with Zenodo sandbox? |
|
I browsed the Python code and it seems reasonable. The action looks reasonable too. I didn't read in-depth but I guess you can check that part. I'd say go ahead and work on it. I wouldn't wait for me to do checking. At the end I would do detailed checks of how the secrets and releases are protected. I have a feeling there might be more we can do, but don't remember details now. Or even if there really was something... maybe it's something else I remember. |
|
this has now been tested with a test repo and on Zenodo sandbox. |
|
Back to draft. Just realized it is missing the pdf upload :tools: |
|
Will put the instructions for maintainers (or whoever will do the releases in future) into manuals. Merging and doing a release to test that all also works in production (as even if it fails nothing really bad is happening, can fix the Zenodo release manually). |
Automation to create new version on ZENODO based on CITATION.cff info when release is done on GitHub.
This does not yet use the new bioschemas metadata, but could be implemented later.
bischemas / cff/ zenodo.json needs some decision first which we could take with maintainers in the future.