Gitlab CI using the wrong entrypoint

Hi, thank you for this tool, it's working perfectly after a small adjustment. The gitlab-ci conf provided in the README needs to be changed to override the entrypoint. Gitlab seems to default to sh which is unavailable:

Created fresh repository.
Checking out 9830bbb9 as v1.1.1...
Skipping Git submodules setup
Executing "step_script" stage of the job script 00:01
Using docker image sha256:5b4bc44275f881eba029c6ab4b044f0b7ee60f9cc31506fa6527d53d50ac25ff for aevea/release-notary:0.9.7 with digest aevea/release-notary@sha256:8df761c1d9225f3fc30a7262a0aedb45162043a1e95406d89246a0fcb1303952 ...
Error: unknown command "sh" for "release-notary"
Run 'release-notary --help' for usage.
unknown command "sh" for "release-notary"
Cleaning up project directory and file based variables 00:01
ERROR: Job failed: exit code 1

It's working after the following change:

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index 369b890..004e938 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -674,7 +674,9 @@ release:
   stage: release
   variables:
     GITLAB_TOKEN: $RELEASE_TOKEN
-  image: aevea/release-notary:0.9.7
+  image:
+    name: aevea/release-notary:0.9.7
+    entrypoint: [""]
   script:
     - release-notary publish
   only:

aevea / release-notary

Gitlab CI using the wrong entrypoint #321