renovate: one PR per chart/image under argo/ instead of one grouped bundle #26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate-ungroup-argocd"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #23. The two
packageRulesit added put every argocd/kubernetes update into the base preset'sdependencies/dependencies-majorgroups, so the Dependency Dashboard (#3) is now holding one PR with 23 packages (cloudnative-pg,external-dns, immich, kro, the four ACK charts, hedgedoc, paperless, docmost, karakeep, meilisearch, vaultwarden, oauth2-proxy, renovate, ...) and a second major one with four.Change (
renovate.jsononly).iam-chartacross the scout/snappy/gw5 Applications,oauth2-proxyacross the two Deployments.quay.io/jetstack/cert-manager-*images grouped ascert-manager. They are cut from one release and the vendored render would be half-upgraded otherwise.prHourlyLimit: 0andprConcurrentLimit: 0. The defaults (2 new PRs per hour, 10 open at once) combined with the preset's first-of-the-month schedule would meter ~25 ungrouped PRs out over several months, which defeats the point. Dial back if the flood is unwelcome.Validated with
renovate-config-validatorfromrenovate/renovate:44.14.9(the version the operator runs).After merge. The queued
renovate/dependenciesandrenovate/major-dependencies-majorbranches have not been created yet (they are only awaiting schedule), so nothing needs closing; the dashboard will re-list them as individual entries on the next hourly run. They still wait for 1 November unless ticked on the dashboard.🤖 Generated with Claude Code