semantic-release / semantic-release/gitlab
Response code 409 (Conflict)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 344
- Forks
- 89
- Avg merge
- 16h 11m
- Merged PRs (30d)
- 4
Description
Using 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.
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
Start with the attached raw log and the @semantic-release/gitlab publish step, comparing the CI invocation with the local command that succeeds. Reproduce the GitLab 409 response and determine whether the conflict condition or the API response can be surfaced more clearly; done means the failure has an identified cause or useful diagnostic output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, javascript
- Domain
- api, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100