Closed viceice closed 3 months ago
I am just configuring a self-hosted renovate runner in Gitlab and can confirm, that none of the limitations apply.
I created a Group Access Token
with scope api
and write_repository
using the role Developer
on a self-hosted Gitlab 15.9.
Configuring an up-to-date renovate container with the RENOVATE_TOKEN
/token
configuration was enough to let it create the dependency dashboard, MRs, ...
Edit: the issue referenced in the issue description mentioned that gitAuthor
has to be set, which I also did. I might do a test with a minimal config later.
Hi, we are using saas gitlab group access token but because of requirements of validated email we are getting error
You can only push commits if the committer email is one of your own verified emails.\nerror: failed to push some refs to
Hi, we are using saas gitlab group access token but because of requirements of validated email we are getting error
You can only push commits if the committer email is one of your own verified emails.\nerror: failed to push some refs to
This is a different issue and can't be fixed from renovate. It's a Gitlab limitation. 🤷♂️
As of GitLab 16.0 group access tokens can only be created with an expiry of one year or less. These docs should highlight the ignorePrAuthor configuration option that needs to be set at when the group access token for Renovate is rotated, otherwise the Renovate run will fail with a bunch "Another open merge request already exists for this source branch" errors.
:tada: This issue has been resolved in version 37.399.2 :tada:
The release is available on:
Your semantic-release bot :package::rocket:
Describe the proposed change(s).
We should add the
Group Access Token
^1 support to the GitLab platform docs. It's confirmed working here^2.Limitations: (needs validation)
RENOVATE_X_PLATFORM_VERSION
configuration