This is helpful, as POST /api/v1/releases returns no HTTP body for a 409 request,
eg when there already is a release for the specified tag.
The underlying problem is bigger:
The Client cannot handle error responses which do not contain a valid JSON body.
I tried to solve it by still printing a usable error message instead of a JSON parsing error
This is helpful, as
POST /api/v1/releasesreturns no HTTP body for a 409 request, eg when there already is a release for the specifiedtag.The underlying problem is bigger: The Client cannot handle error responses which do not contain a valid JSON body. I tried to solve it by still printing a usable error message instead of a JSON parsing error