Update dependency renovate-bot/renovate-runner to v20 (main)
This MR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
renovate-bot/renovate-runner | repository | major |
v19.111.4 -> v20.0.0
|
Release Notes
renovate-bot/renovate-runner (renovate-bot/renovate-runner)
v20.0.0
⚠️ BREAKING CHANGES
- Renovate image is only pinned to major version docker tag. Additionally the
pull_policy
is set toalways
to force image updates. This requires GitLab 15.4.
Features
- only pin renovate image to major version (renovate-bot/renovate-runner!3294 (merged)) (86f5f6a)
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot Sylva instance.
CI configuration
Below you can choose test deployment variants to run in this MR's CI.
Click to open to CI configuration
Legend:
Icon | Meaning | Available values |
---|---|---|
Infra Provider |
capd , capo , capm3
|
|
Bootstrap Provider |
kubeadm (alias kadm ), rke2
|
|
Node OS |
ubuntu , suse
|
|
Deployment Options |
light-deploy , dev-sources , ha , misc
|
|
Pipeline Scenarios | Available scenario list and description |
-
🎬 preview☁️ capd🚀 kadm🐧 ubuntu -
🎬 preview☁️ capo🚀 rke2🐧 suse -
🎬 preview☁️ capm3🚀 rke2🐧 ubuntu -
☁️ capd🚀 kadm🛠️ light-deploy🐧 ubuntu -
☁️ capd🚀 rke2🛠️ light-deploy🐧 suse -
☁️ capo🚀 rke2🐧 suse -
☁️ capo🚀 kadm🐧 ubuntu -
☁️ capo🚀 rke2🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capo🚀 kadm🎬 wkld-k8s-upgrade🐧 ubuntu -
☁️ capo🚀 rke2🎬 rolling-update-no-wkld🛠️ ha,misc🐧 suse -
☁️ capo🚀 rke2🎬 sylva-upgrade-from-1.3.x🛠️ ha,misc🐧 ubuntu -
☁️ capm3🚀 rke2🐧 suse -
☁️ capm3🚀 kadm🐧 ubuntu -
☁️ capm3🚀 kadm🎬 rolling-update-no-wkld🛠️ ha,misc🐧 ubuntu -
☁️ capm3🚀 rke2🎬 wkld-k8s-upgrade🛠️ ha🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 ubuntu -
☁️ capm3🚀 rke2🎬 sylva-upgrade-from-1.3.x🛠️ misc,ha🐧 suse -
☁️ capm3🚀 kadm🎬 rolling-update🛠️ ha🐧 suse
Global config for deployment pipelines
-
autorun pipelines -
allow failure on pipelines
Notes:
- Enabling
autorun
will make deployment pipelines to be run automatically without human interaction - Disabling
allow failure
will make deployment pipelines mandatory for pipeline success. - if both
autorun
andallow failure
are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline
Be aware: after configuration change, pipeline is not triggered automatically.
Please run it manually (by clicking the run pipeline
button in Pipelines tab) or push new code.