semantic-release / semantic-release/gitlab
HTTPError: Response code 404 (Not Found)
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 344
- Forks
- 89
- Avg merge
- 16h 11m
- Merged PRs (30d)
- 4
Description
[semantic-release] [@semantic-release/gitlab] › ✖ An error occurred while making a request to the GitLab release API:
HTTPError: Response code 404 (Not Found)
at Request.<anonymous> (/comoponent-lib/node_modules/got/dist/source/as-promise/index.js:117:42)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
code: undefined,
timings: {
start: 1636370892010,
socket: 1636370892010,
lookup: 1636370892012,
connect: 1636370892013,
secureConnect: 1636370892013,
upload: 1636370892014,
response: 1636370892023,
end: 1636370892023,
error: undefined,
abort: undefined,
phases: {
wait: 0,
dns: 2,
tcp: 1,
tls: 0,
request: 1,
firstByte: 9,
download: 0,
total: 13
}
}
}
[11:28:12 AM] [semantic-release] › ✖ Failed step "publish" of plugin "@semantic-release/gitlab"
.releaserc
{
"branches": [
"+([0-9])?(.{+([0-9]),x}).x",
"master",
"next",
"next-major",
],
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/changelog",
"@semantic-release/npm",
"@semantic-release/git",
[
"@semantic-release/gitlab",
{
"assets": [
{ "path": "build/**/*", "label": "Compiled files" }
]
}
]
]
}
gitlab version: v11.4.0
"@semantic-release/changelog": "^6.0.1",
"@semantic-release/git": "^10.0.1",
"@semantic-release/gitlab": "^7.0.4",
"@semantic-release/npm": "^8.0.3",
"semantic-release": "^18.0.0"
Thanks for your help.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review .releaserc and the @semantic-release/gitlab publish step, then trace the request to the GitLab release API that returns 404. Confirm the release target can be reached with the shown configuration and that publishing completes without the error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, javascript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100