Skip to content

Commit

Permalink
docs: Add update to gitlab-bot-security page (#15650)
Browse files Browse the repository at this point in the history
  • Loading branch information
tennox committed May 19, 2022
1 parent 768e178 commit 4e0cb04
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions docs/usage/gitlab-bot-security.md
Expand Up @@ -80,9 +80,14 @@ Bot services are better if they are provisioned with a "bot identity" so that us
Until the hosted app can be reactivated, we recommend users migrate to use self-hosted pipelines to run Renovate.
Please see the [renovate-bot/renovate-runner README on GitLab](https://gitlab.com/renovate-bot/renovate-runner/-/blob/HEAD/README.md) for instructions on how to set this up as easily as possible.

## Status of the Renovate app for GitLab

We're trying to find a workable design for the GitLab app, so we can enable it safely again.
If you have any ideas, open a [discussion](https://github.com/renovatebot/renovate/discussions) and let us know!

GitLab introduced Group Access Tokens & API for paid & self-hosted instances, but a good permission setup/flow is still not possible.
Check out [GitLab issue #346298](https://gitlab.com/gitlab-org/gitlab/-/issues/346298).

## Acknowledgments

Thank you to Nejc Habjan for bringing this security challenge to our attention, and also to his colleagues at Siemens for their help researching the risks.
Expand Down

0 comments on commit 4e0cb04

Please sign in to comment.