From 6104056f0d60fc5ac1d7ea19d7aa9e141237254b Mon Sep 17 00:00:00 2001
From: h <h@kotikot.com>
Date: Tue, 15 Sep 2026 21:06:54 +0000
Subject: [PATCH] feat(automerge): automerge code dependencies, majors after
 dashboard approval

---
 README.md    | 9 +++++----
 default.json | 4 ++--
 2 files changed, 7 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 7bf78e2..87f9964 100644
--- a/README.md
+++ b/README.md
@@ -17,10 +17,11 @@ Use it from a project repo as the whole of its `renovate.jsonc`:
 What it does: docker digests, patches and minors merge themselves after a
 three day wait; docker majors and database majors wait for a click on the
 dependency dashboard; code dependencies (npm, pip, go.mod, actions) are
-collected into one pull request per repo and never merge themselves. Registries
-without a release timestamp get the `wait-3d` label instead, and the age gate
-merges those. The edge (`caddy/**`), `_legacy/**` and worktree compose files are
-out of scope.
+collected into one pull request per repo, which merges itself after the same
+three day wait; code majors wait for a click on the dependency dashboard and
+merge themselves once approved. Registries without a release timestamp get the
+`wait-3d` label instead, and the age gate merges those. The edge (`caddy/**`),
+`_legacy/**` and worktree compose files are out of scope.
 
 The repo has to carry the `renovate`, `wait-3d` and `deps-code` labels before
 the first run: Renovate fails on a label that does not exist.
diff --git a/default.json b/default.json
index d9b78d2..34bc8ee 100644
--- a/default.json
+++ b/default.json
@@ -125,7 +125,7 @@
         "pinDigest"
       ],
       "groupName": "code dependencies",
-      "automerge": false,
+      "automerge": true,
       "addLabels": [
         "deps-code"
       ]
@@ -137,7 +137,7 @@
       "matchUpdateTypes": [
         "major"
       ],
-      "automerge": false,
+      "automerge": true,
       "dependencyDashboardApproval": true
     }
   ]