-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in request to create release #192
Comments
Thanks for this detailed report @tacnoman! It's interesting, because the Is it possible that one of the asset's names is coming through as 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 Even if this does work, this sounds like a bug to me. |
Attempting to fix semantic-release#192
@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 "@semantic-release/gitlab": "^6.0.8" with this:
and rerun (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 |
Meet the same issue. |
It should be similar to my question, and I have submitted a PR and it is waiting for review |
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:
|
Hello everyone
I'm receiving an error when I run the semantic release in last step. The code can create the tag, but after this, there is a request to
/release
that I'm receiving a 400 error codeI start to investigate the problem in code and I put a debug with error message in API:
Is required a field called
name
in json data send with GOT.gitlab/lib/publish.js
Lines 73 to 87 in f8957c3
There is no field called
name
in this fileI changed and add a name with any value and I received a 201 code.
Is this a bug, different version or I made something wrong?
Thanks for this
The text was updated successfully, but these errors were encountered: