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.263.1
ref: v17.264.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 `v17.263.1` tag.
The following sample uses the `v17.264.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/v17.263.1/templates/renovate.gitlab-ci.yml
- remote: https://gitlab.com/renovate-bot/renovate-runner/-/raw/v17.264.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:37.415.0@sha256:3c13c894914130d7052d56eedfc0a7a8c2bdec3015248c1ae3cf78d422a2afbb
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:37.416.1@sha256:f2d7f6204d85539a8a81b4d8727f1d25e1b7f4bf751a317b041e623e2110514e
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.415.0@sha256:3c13c894914130d7052d56eedfc0a7a8c2bdec3015248c1ae3cf78d422a2afbb
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:37.416.1@sha256:f2d7f6204d85539a8a81b4d8727f1d25e1b7f4bf751a317b041e623e2110514e
.renovate:
cache:
......