Tracing back the cause, as described in the issue above, it was due to the type definition of gitbeaker's Release.description, which node-gitlab-2-github just trusts it. I asked gitbeaker's author to fix it and he has already fixed it. Therefore, the problem will be resolved if node-gitlab-2-github uses gitbeaker 39.7.0, which would (unfortunately) need some other changes.
Hi. Thanks for maintaining this awesome tool.
Migration of GitLab releases fails if
descriptionfield is null. This is because GitLab assumesnullfor an optional field but node-gitlab-2-github doesn'tTracing back the cause, as described in the issue above, it was due to the type definition of gitbeaker's
Release.description, which node-gitlab-2-github just trusts it. I asked gitbeaker's author to fix it and he has already fixed it. Therefore, the problem will be resolved if node-gitlab-2-github uses gitbeaker 39.7.0, which would (unfortunately) need some other changes.