Thanks for this detailed report @tacnoman!

It's interesting, because the name field is optional in GitLab's Release API: https://docs.gitlab.com/ee/api/releases/#create-a-release 🤔

Is it possible that one of the asset's names is coming through as null/undefined? The name property is required on each asset link object.

In the code you linked to, I see the asset name is being populated like this:

name: label || alt, 

Perhaps these are both falsy for some reason 🤔

Assuming you are including assets with your release, could you try adding a label in your configuration file as described here?

Even if this does work, this sounds like a bug to me.

@tacnoman I put together a quick branch in my fork that logs the JSON being sent to the GitLab API. (Here's the commit.)

If you replace your this line in your package.json:

"@semantic-release/gitlab": "^6.0.8"

with this:

"@semantic-release/gitlab": "nfriend/gitlab#debugging-issues-192"

and rerun npm install and your deploy, you should see the JSON printed in your logs. If this works for you, would you mind posting the JSON here?

(Disclaimer: I haven't tested this, so it's possible it might not work 😅)

I got the same problem. And I try to set name in publish.js and it works at localhost.

I got the same problem. code 400

I tried to add the attribute "name" to the body, and the result was successful. I hope to optimize it as soon as possible, I think it may be a bug, thank you

Meet the same issue.
And the Gitlab version is: 13.6.1

It should be similar to my question, and I have submitted a PR and it is waiting for review
#239

Any update?

I solved creating a new file with name and in pipeline after install I replace the file

Release:
    ......
    script:
        - cp ./publish.js /usr/local/lib/node_modules/@semantic-release/gitlab/lib/publish.js
        - DEBUG=semantic-release:gitlab npx semantic-release

I copied the publish.js to my project folder and added a parameter name, like this:

//...... line 75
     json: {
        /* eslint-disable camelcase */
        tag_name: gitTag,
        name: `Bump tag: ${gitTag}`, // Added this line
        description: notes && notes.trim() ? notes : gitTag,
        assets: {
// ......

@renatocassino @merlosy I am successfully using this plugin with our self-hosted GitLab instance. Can you share more details of your setup to help understand what could be the reason for your issues?

Possibly interesting information:

• Your semantic-release config
• Version and flavor of your GitLab instance
• Your build/release pipeline