From 4d59c63b73145551ba9138989574738724ea4474 Mon Sep 17 00:00:00 2001 From: Toby Pettit <9166525+tobydoescode@users.noreply.github.com> Date: Tue, 28 Jul 2026 16:54:20 +0100 Subject: [PATCH] chore(renovate): gate patch automerge on release age and use platform automerge Now that CI runs on every PR, Renovate's automerge has real checks to wait on. Two adjustments: - platformAutomerge delegates the merge to GitHub's native auto-merge, so an automergeable PR lands as soon as the checks go green rather than waiting for Renovate's next scheduled run. Requires the repo auto-merge setting, which has been enabled. - Patch updates had no minimumReleaseAge, so a release could automerge minutes after publication. 3 days leaves room for a bad release to be yanked or hotfixed before it lands here. Minor and major are unchanged: still manual, still 7 and 30 day gates. Co-Authored-By: Claude Opus 5 --- renovate.json | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/renovate.json b/renovate.json index c2f5da1..e700de6 100644 --- a/renovate.json +++ b/renovate.json @@ -2,10 +2,12 @@ "$schema": "https://docs.renovatebot.com/renovate-schema.json", "extends": ["config:recommended"], "assignees": ["tobydoescode"], + "platformAutomerge": true, "packageRules": [ { "matchUpdateTypes": ["patch"], - "automerge": true + "automerge": true, + "minimumReleaseAge": "3 days" }, { "matchUpdateTypes": ["minor"],