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: v17.288.2
ref: v17.288.3
```
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 `v17.288.2` tag.
The following sample uses the `v17.288.3` 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/v17.288.2/templates/renovate.gitlab-ci.yml
- remote: https://gitlab.com/renovate-bot/renovate-runner/-/raw/v17.288.3/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:37.440.5@sha256:9b51d3d092ffd56b8786648a90a978a8abd8ddbd6f8f9e176b21f6c8d2c2a94d
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:37.440.6@sha256:68312dd985319bfe9c5aa2628e1f523761af182b6cc95dcb61cad3d98327efc1
renovate-config-validator:
stage: test
......
......@@ -7,7 +7,7 @@ variables:
RENOVATE_REPOSITORY_CACHE: 'enabled'
RENOVATE_LOG_FILE: renovate-log.ndjson
RENOVATE_LOG_FILE_LEVEL: debug
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:37.440.5@sha256:9b51d3d092ffd56b8786648a90a978a8abd8ddbd6f8f9e176b21f6c8d2c2a94d
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:37.440.6@sha256:68312dd985319bfe9c5aa2628e1f523761af182b6cc95dcb61cad3d98327efc1
.renovate:
cache:
......