fix(renovate): raise memory cap to 3g + alert on failed runs (#87) #88

Sammanfogat

supernaut sammanfogade 1 incheckning från renovate-oom-fix in i main

2026-07-17 20:29:32 +00:00

supernaut kommenterad

2026-07-17 16:42:14 +00:00

Ägare

renovate_memory_max: 1.5g → 3g (peak RSS pinned at exactly the old cap on every failed run; 1.5g was already borderline before the failures started).
New RenovateRunFailed alert on gitborg_renovate_last_run_status != 0 — the metric was added for exactly this (tenant-Renovate plan §3.2) but nothing watched it, which is how 7 consecutive failures went unnoticed.

After merge+apply: next nightly run should process bitborg-web and open all pending PRs at once (the "create all" dashboard checkbox is already ticked). Verify gitborg_renovate_last_run_status returns 0 and the bitborg-web dashboard body refreshes.

Fixes #87. The nightly Renovate run has been OOM-killed (exit 137) at the 1.5 GiB container cap every night since 2026-07-11 — dying exactly at bitborg-web (repo 4/5), so bitborg-web and the tenant repo after it silently got no updates while earlier repos looked fine. - `renovate_memory_max: 1.5g → 3g` (peak RSS pinned at exactly the old cap on every failed run; 1.5g was already borderline before the failures started). - New `RenovateRunFailed` alert on `gitborg_renovate_last_run_status != 0` — the metric was added for exactly this (tenant-Renovate plan §3.2) but nothing watched it, which is how 7 consecutive failures went unnoticed. After merge+apply: next nightly run should process bitborg-web and open all pending PRs at once (the "create all" dashboard checkbox is already ticked). Verify `gitborg_renovate_last_run_status` returns 0 and the bitborg-web dashboard body refreshes.

supernaut lade till 1 incheckning

2026-07-17 16:42:14 +00:00

fix(renovate): raise memory cap to 3g + alert on failed runs (#87 )

ci / ci (pull_request) Successful in 1m26s

Detaljer

e5383a47df