-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Help] An error occurred while making a request to the GitLab release API: HTTPError: Response code 403 (Forbidden) #734
Comments
Thanks for the detailed description @felixprado-mc! I have not yet of heard of such issues, so let's start with a few basic questions:
|
Hi @fgreinacher , I appreciate your interest. 1, 2, 3, The project is hosted on gitlab.com but it's private so I can't share it. What should be the scope/permissions for the GL_TOKEN? If this adds more information, we run this step in a Gitlab CI pipeline with the following commands:
|
Thanks for sharing some details! You could start very simple like this:
And if that works add your configuration options one-by-one until it starts failing. |
Hi @felixprado-mc, regarding 4:
|
Hi @JonasSchubert. Thanks for the support.
The tokens are different ones, but they have the same permissions (they are created centrally with Terraform). Regarding the repository configuration, I've checked multiple times the protected branches or tags, the users that have permission to commit (including the token) and I see no difference.
All of them are private.
It is specifically allowed for the token.
No, the tokens were created after the repository was created.
I ran out of ideas of what is causing this, that's why I opened this thread. What is even stranger is that it fails in the first attempt, but works on the second. |
I have the same issue. @felixprado-mc Do you resolve this problem? |
I'm also having this issue after upgrading semantic-release.
at the bottom I see an even stranger:
which is odd because nowhere in my repo do I use the github plugin:
I do have GITLAB_TOKEN set however, per the README |
I get this error when executing the plugin in a Gitlab CI pipeline. It only happens the first time, because in the second execution it works fine.
I have a GL_TOKEN with the right permissions over the project.
Could anyone help?
This is the .releaserc file of the project:
and the package.json:
The text was updated successfully, but these errors were encountered: