Release-cli v0.10.0 fails to parse date

Summary

Job fails with error message that dates not properly parsed when no released-at value provided in release-cli v0.10.0.

Update: The release is actually created, but the jobs fails.

Steps to reproduce

Try to create release with no released-at value provided (that at least seems to be the common theme). The job fails, but the release is actually created. This occurred for me in two projects today my own release tool that parses a JSON file and changelog to create script for release-cli.

Example Project

When trying to create a release the following error is seen:

$ sh .gitlab/release.sh
time="2021-09-12T17:38:26Z" level=info msg="Creating Release..." cli=release-cli command=create name="2.1.1 (2021-09-12)" project-id=16325541 ref=e534169d442acf2da700c46a7d07f7eb51233b45 server-url="https://gitlab.com" tag-name=2.1.1 version=0.10.0
time="2021-09-12T17:38:26Z" level=fatal msg="run app" cli=release-cli error="failed to create release: failed to decode response: parsing time \"null\" as \"2006-01-02\": cannot parse \"null\" as \"2006\"" version=0.10.0

The .gitlab/release.sh script in question is:

#!/bin/sh
release-cli create --name '2.1.1 (2021-09-12)' --description '### Fixed

- Updated to latest dependencies

### Miscellaneous

- Configured [renovate](https://docs.renovatebot.com/) for dependency updates (#25)' --tag-name 2.1.1 --assets-link '{"name":"npm","url":"https://www.npmjs.com/package/releaselog","type":"package"}' --milestone "${CI_COMMIT_TAG}"

The specific log can be seen at https://gitlab.com/gitlab-ci-utils/releaselog/-/jobs/1583213074.

What is the current bug behavior?

Release-cli creates release, but the job fails.

What is the expected correct behavior?

Release-cli job should not fail.

Output of checks

This bug happens on GitLab.com.