New Github releases not triggering new Zenodo version

[martintoreilly]

Problem

A (now draft) v0.2 Github release looks like it didn't trigger an automatic v0.2 Zenodo version. The v0.2 Zenodo version still links to the v0.1 Github version as the "supplement to" in the "related identifiers" box and when I look at the entry for the linked code-cite repo in the Github section of my Zenodo account I see three entries for a v0.3 Github release with a "failed" status (see screenshot below).

Clicking on one of the "failed" statuses and then the "Errors" tab gives the following detail.

{
    "errors": "Metadata file \".zenodo.json\" is not valid JSON."
}

Solution

I think the issue is an escaped single quote in the description field of the .zenodo.json file (i.e. "Software Sustainability Institute\'s" rather than "Software Sustainability Institute's").

With the \' the file fails validation with the following error when I try and validate it on https://codebeautify.org/jsonvalidator. With the ' unescaped, the file validates.

Error: Parse error on line 2:
{	"description": "<p>This version of 
-----------------^
Expecting 'STRING', 'NUMBER', 'NULL', 'TRUE', 'FALSE', '{', '[', got 'undefined'

Also, the string state machine on json.org does not show single quote as an escaped character (via this Stackoverflow article).

[martintoreilly]

Fix submitted via PR #33.

[tueda]

Maybe this is a similar issue, maybe not, but I got an Unknown error on a GitHub release today: