Skip to content
Commits on Source (2)
......@@ -64,7 +64,7 @@ To prevent unexpected changes in your pipeline, you can pin the version of this
include:
- project: 'renovate-bot/renovate-runner'
file: '/templates/renovate.gitlab-ci.yml'
ref: v18.61.1
ref: v18.63.0
```
Please check this project's [Releases page](https://gitlab.com/renovate-bot/renovate-runner/-/releases)
......@@ -87,14 +87,14 @@ renovate:
```
You can now use remote includes to use these templates on self-hosted gitlab instances.
The following sample uses the `v18.61.1` tag.
The following sample uses the `v18.63.0` tag.
You can also use `main` branch but a tag is preferred.
Refer to GitLab [include](https://docs.gitlab.com/ee/ci/yaml/includes.html) samples for more information.
You can add `gitlab>renovate-bot/renovate-runner` to your repos `renovate.json>extends` array to automatically update the runner version.
```yaml
include:
- remote: https://gitlab.com/renovate-bot/renovate-runner/-/raw/v18.61.1/templates/renovate.gitlab-ci.yml
- remote: https://gitlab.com/renovate-bot/renovate-runner/-/raw/v18.63.0/templates/renovate.gitlab-ci.yml
```
## Configure the Schedule
......
variables:
RENOVATE_ENDPOINT: $CI_API_V4_URL
RENOVATE_PLATFORM: gitlab
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:38.100.0@sha256:02f70f8f117e7948ea557f6758a37e1eb95015b0d89ad30f041b0ef23638b633
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:38.100.1@sha256:5f51c05a4b017c26d4eeb8f44b6c7346dbd8d32e87ba4a3b9448bacdcf7e3d9c
renovate-config-validator:
stage: test
......
......@@ -7,7 +7,7 @@ variables:
RENOVATE_REPOSITORY_CACHE: 'enabled'
LOG_FILE: renovate-log.ndjson
LOG_FILE_LEVEL: debug
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:38.100.0@sha256:02f70f8f117e7948ea557f6758a37e1eb95015b0d89ad30f041b0ef23638b633
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:38.100.1@sha256:5f51c05a4b017c26d4eeb8f44b6c7346dbd8d32e87ba4a3b9448bacdcf7e3d9c
.renovate:
cache:
......