-
Renovate Bot authored
| datasource | package | from | to | | --------------- | ---------------------------- | -------- | -------- | | gitlab-releases | renovate-bot/renovate-runner | v18.68.3 | v18.69.0 |
Renovate Bot authored| datasource | package | from | to | | --------------- | ---------------------------- | -------- | -------- | | gitlab-releases | renovate-bot/renovate-runner | v18.68.3 | v18.69.0 |
Renovate Runner
The intention of this project is to provide a pipeline which is easy to set up and reflects the current app settings as close as possible.
You will need to:
- Create a new project to host the runner
- Configure credentials using CI variables
- Create a new
main
pipeline that includes this project's template - Set up a schedule to run the pipeline regularly
Create a new Runner project
We recommend you use a new and dedicated private project to host the Renovate runner, however a public project with private CI logs should still be safe.
Configure CI/CD variables
You need to add a GitLab Personal Access Token (scopes: read_user
, api
and write_repository
) as RENOVATE_TOKEN
to CI/CD variables.
You can also use a GitLab Group Access Token.
Checkout Renovate platform docs and #53 for more information.
It is also recommended to configure a GitHub.com Personal Access Token (minimum scopes) as GITHUB_COM_TOKEN
so that your bot can make authenticated requests to github.com for Changelog retrieval as well as for any dependency that uses GitHub tags.
Without such a token, github.com's API will rate limit requests and make such lookups unreliable.
Finally, you need to decide how your bot should decide which projects to run against.
By default renovate won't find any repo, you need to choose one of the following options for RENOVATE_EXTRA_FLAGS
.