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

[damdafayton]

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

[damdafayton]

Solved it by:

• Removing all the assets from "@semantic-release/gitlab" in .releaserc.json
• Adding git fetch --prune-tags to .gitlab-ci.yml
• removing latest tag from local and origin

Though dont know which one exactly solved the issue.

[damdafayton]

Ok still getting this error. Its really annoying. No detailed information of why its failing. Only this.

emote: Retry later
fatal: unable to access 'https://gitlab.***/': The requested URL returned error: 429

[fgreinacher]

Status code 429 indicates that you're sending too many requests to GitLab. Is that GitLab instance under your control? If so you could you check which rate limits are configured?