Update dependency renovate-bot/renovate-runner to v19.111.4 (main)

This MR contains the following updates:

Package	Type	Update	Change
renovate-bot/renovate-runner	repository	minor	v19.107.1 -> v19.111.4

---

Release Notes

renovate-bot/renovate-runner (renovate-bot/renovate-runner)

v19.111.4

Compare Source

Bug Fixes

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.161.6 (renovate-bot/renovate-runner!3293 (merged)) (e334178)

Miscellaneous Chores

• renovate: disable renovate image pinning on templates (1c61d23)
• renovate: reconfigure renovate (c744c30)

v19.111.3

Compare Source

Bug Fixes

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.161.5 (renovate-bot/renovate-runner!3292 (merged)) (89a258a)

v19.111.2

Compare Source

Bug Fixes

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.161.4 (renovate-bot/renovate-runner!3291 (merged)) (3ccd534)

v19.111.1

Compare Source

Bug Fixes

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.161.1 (renovate-bot/renovate-runner!3290 (merged)) (3f151a0)

v19.111.0

Compare Source

Features

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.161.0 (renovate-bot/renovate-runner!3289 (merged)) (0b1fd1e)

Miscellaneous Chores

• deps: update ghcr.io/containerbase/node docker digests to fa74189 (970ba57)

v19.110.0

Compare Source

Features

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.160.1 (renovate-bot/renovate-runner!3288 (merged)) (e25ddf9)

v19.109.0

Compare Source

Features

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.159.0 (renovate-bot/renovate-runner!3287 (merged)) (593e3b2)

v19.108.1

Compare Source

Bug Fixes

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.158.2 (renovate-bot/renovate-runner!3286 (merged)) (3a5d21d)

Documentation

• deps: update dependency renovate-runner to v19.108.0 (f8a8b10)

Miscellaneous Chores

• deps: update ghcr.io/containerbase/node docker digests to 6582722 (0034b0d)

v19.108.0

Compare Source

Features

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.158.1 (renovate-bot/renovate-runner!3285 (merged)) (1549cdd)

v19.107.2

Compare Source

Bug Fixes

• deps: update ghcr.io/renovatebot/renovate docker tag to v39.156.2 (renovate-bot/renovate-runner!3284 (merged)) (1b27fde)

Documentation

• deps: update dependency renovate-runner to v19.107.1 (c0c0924)

Miscellaneous Chores

• deps: lock file maintenance (b644d46)

---

Configuration

📅 Schedule: Branch creation - "before 4am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻️ Rebasing: Whenever MR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

---

• 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 and allow 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.

⚙️ If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)