Response code 409 (Conflict)
See original GitHub issueUsing GitLab 14, on Semantic-Release 17.4.4. I’m still getting this Error 409. It would be great if nothing else to have more information than --debug
provides,
The bottom reads,
[4:36:12 PM] [semantic-release] [@semantic-release/gitlab] › ✖ An error occurred while making a request to the GitLab release API:
HTTPError: Response code 409 (Conflict)
at EventEmitter.<anonymous> (/usr/local/lib/node_modules/@semantic-release/gitlab/node_modules/got/dist/source/as-promise.js:118:31)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
[4:36:12 PM] [semantic-release] › ✖ Failed step "publish" of plugin "@semantic-release/gitlab"
[4:36:12 PM] [semantic-release] › ✖ An error occurred while running semantic-release: HTTPError: Response code 409 (Conflict)
at EventEmitter.<anonymous> (/usr/local/lib/node_modules/@semantic-release/gitlab/node_modules/got/dist/source/as-promise.js:118:31)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
pluginName: '@semantic-release/gitlab'
}
HTTPError: Response code 409 (Conflict)
at EventEmitter.<anonymous> (/usr/local/lib/node_modules/@semantic-release/gitlab/node_modules/got/dist/source/as-promise.js:118:31)
at runMicrotasks (<anonymous>)
at processTicksAndRejections (node:internal/process/task_queues:96:5) {
pluginName: '@semantic-release/gitlab'
}
This works locally when I run,
CI=1 GITLAB_TOKEN=token npx semantic-release --publish --ci
So I’m at a loss for why it wouldn’t work on the smoker.
[5:16:28 PM] [semantic-release] › ℹ Running semantic-release version 17.4.4
[5:16:29 PM] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/gitlab"
[5:16:29 PM] [semantic-release] › ✔ Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[5:16:29 PM] [semantic-release] › ✔ Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[5:16:29 PM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/gitlab"
[5:16:31 PM] [semantic-release] › ✔ Run automated release from branch master on repository https://gitlab-ci-token:[secure]@gitlab.awe.eco.acme.net/ec-ng-ui/angular-validators.git
[5:16:31 PM] [semantic-release] › ✔ Allowed to push to the Git repository
[5:16:31 PM] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/gitlab"
[5:16:31 PM] [semantic-release] [@semantic-release/gitlab] › ℹ Verify GitLab authentication (https://gitlab.awe.eco.acme.net/api/v4)
[5:16:32 PM] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/gitlab"
[5:16:32 PM] [semantic-release] › ℹ No git tag version found on branch master
[5:16:32 PM] [semantic-release] › ℹ No previous release found, retrieving all commits
[5:16:32 PM] [semantic-release] › ℹ Found 480 commits since last release
[5:16:32 PM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
...
I’ve uploaded more of the log for context.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5
Top Results From Across the Web
How To Fix the “409 Conflict” Error (5 Methods) - Kinsta
If you see a “409 Conflict” error, this is a 400 HTTP status code. In short, the request wasn't completed because of a...
Read more >409 Conflict - HTTP Status Code Glossary - WebFX
What Is a 409 Status Code? ... The request could not be completed due to a conflict with the current state of the...
Read more >Reasons for a 409/Conflict HTTP error when uploading a file ...
For example, you may get a 409 error if you try to upload a file to the Web server which is older than...
Read more >409 CONFLICT HTTP Status Code
409 CONFLICT HTTP: The request could not be completed due to a conflict with the current state of the target resource. This code...
Read more >What is HTTP Status Code 409 (Conflict)? - Abstract API
Examples of conflicts that could result in an HTTP Status Code 409 include an edit conflict on a given resource as a result...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@ericschmar I believe what @kphunter is saying is he had to use the GitLab Releases API to delete the corresponding releases. But tagging him will help get an answer to that. 😉
That’s correct - either remove the GitLab Release via the API or manually through the UI to get rid of the reference that is causing the conflict.