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: v19.8.1
ref: v19.9.1
```
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 `v19.8.1` tag.
The following sample uses the `v19.9.1` 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/v19.8.1/templates/renovate.gitlab-ci.yml
- remote: https://gitlab.com/renovate-bot/renovate-runner/-/raw/v19.9.1/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:39.18.2@sha256:52f3ceeedc00d67cacc9875371201bd93c2c9173a4102999b2bb6d5fd58fde43
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:39.18.3@sha256:2532a16ab772ece0b39957340479bca71f4154dc4879d71d81f0483a4529e5ff
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:39.18.2@sha256:52f3ceeedc00d67cacc9875371201bd93c2c9173a4102999b2bb6d5fd58fde43
CI_RENOVATE_IMAGE: ghcr.io/renovatebot/renovate:39.18.3@sha256:2532a16ab772ece0b39957340479bca71f4154dc4879d71d81f0483a4529e5ff
.renovate:
cache:
......