semantic-release / semantic-release/gitlab

An error occurred while running semantic-release: Error: Command failed with exit code 128:

Open
#529 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

support
Dominant language
JavaScript
Stars
344
Forks
89
Avg merge
16h 11m
Merged PRs (30d)
4

Description

Current behavior

I am getting this error too often.

Sometimes if I delete the tags manually it makes new publish. On my last try 5 consecutive trials have failed. Its very annoying. Almost 50% of my release attempts fail by this error and Its not even clear why it fails.

Expected behavior

make new release

semantic-release version

^17.3.0

CI environment

gitlab

Plugins used
"@semantic-release/git": "^9.0.0",
"@semantic-release/gitlab": "^6.0.5",
"@semantic-release/npm": "^7.0.8",
semantic-release configuration

{
"branches": [
"master"
],
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
[
"@semantic-release/gitlab",
{
"assets": [
{
"path": "index.js",
"label": "Module"
},
{
"path": "README.md",
"label": "Documentation"
},
{
"path": "LICENSE",
"label": "License"
}
]
}
],
"@semantic-release/npm",
[
"@semantic-release/git",
{
"assets": [
"package.json"
],
"message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
}
]
]
}

CI logs

An error occurred while running semantic-release: Error: Command failed with exit code 128: git push [https://gitlab-ci-token:[secure]@gitlab***](https://gitlab-ci-token:%5Bsecure%5D@gitlab***) refs/notes/semantic-release remote: Retry later fatal: unable to access 'https://gitlab***': The requested URL returned error: 429

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CI log showing the git push to refs/notes/semantic-release and the GitLab 429 response. Review the listed semantic-release plugins and configuration, then compare successful and failed release attempts to identify the failure condition. Done means documenting an actionable cause and verifying that releases no longer fail intermittently or require manual tag deletion.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, gitlab, javascript
Domain
ci-cd, devops, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.