Skip to content



First, create a Personal Access Token for the bot account.

For real runs, give the PAT these scopes:

For dry runs, give the PAT these scopes:

  • read_user
  • read_api
  • read_repository
  • write_repository (when using autodiscover)
  • read_registry (only if Renovate needs to access the GitLab Container registry)

Let Renovate use your PAT by doing one of the following:

  • Set your PAT as a token in your config.js file
  • Set your PAT as an environment variable RENOVATE_TOKEN
  • Set your PAT when you run Renovate in the CLI with --token=

Remember to set platform=gitlab somewhere in your Renovate config file.

If you're using a private GitLab container registry, you must:

  • Set the RENOVATE_HOST_RULES CI variable to [{"matchHost": "${CI_REGISTRY}","username": "${GITLAB_USER_NAME}","password": "${RENOVATE_TOKEN}", "hostType": "docker"}].
  • Make sure the user that owns the RENOVATE_TOKEN PAT is a member of the corresponding GitLab projects/groups with the right permissions.
  • Make sure the RENOVATE_TOKEN PAT has the read_registry scope.

Features awaiting implementation

  • The automergeStrategy configuration option has not been implemented for this platform, and all values behave as if the value auto was used. Renovate will accept the Merge Request without further configuration, and respect the strategy defined in the Merge Request, and this cannot be overridden yet

Server version dependent features

We use the GitLab version API to fetch the server version. You can use the experimental feature flag RENOVATE_X_PLATFORM_VERSION to set a specific server version. By setting the server version yourself, you save a API call that fetches the server version.

  • Use Draft: MR prefix instead of WIP: prefix since v13.2.0
  • Do not truncate Markdown body to 25K chars since v13.4.0
  • Allow configure reviewers since v13.9.0

Multiple merge request assignees

Due to licensing restrictions multiple assignees are only available in GitLab Premium self-managed, GitLab Premium SaaS, and higher tiers. Because of a safeguard in GitLab's API if multiple assignees are set, but not available to the project, only the first assignee will be applied.

Open items

The below list of features and bugs were current when this page was generated on June 06, 2023.

Feature requests

  • Use GitLab platform token for container registry #17940
  • Set assignees on PR creation for better Gitlab webhook events #17620
  • Warning as thread instead of regular note for GitLab #15985
  • Gitlab - autodiscover by groups #12635
  • [GitLab] Change email source in gitAuthor #12532
  • Implement the explicit automergeStrategy for the Gitlab platform. #10870
  • Assign GitLab MRs on creation and not as update #9252
  • Conflict between Gitlab @ mentions feature and Fix Renovate Configuration issue #8030
  • Support GitLab "merge trains" #5573
  • Feature request: GitLab forkMode #840

Bug reports

  • Release Notes replace all occurrences of PR with MR #20682