From 82eb19d167ffe9d262a469f571c1c65bfe2eae15 Mon Sep 17 00:00:00 2001 From: Claude Date: Thu, 18 Jun 2026 13:02:19 +0000 Subject: [PATCH] chore: switch Renovate lock-file maintenance & dev-deps to PR automerge `lockFileMaintenance` and the "major/minor dev dependencies" rule used `automergeType: "branch"`, which never opens a PR and relies on branch automerge merging directly into `master` once branch status checks pass. But CI only runs on `pull_request` and pushes to `master`, so no checks ever run on `renovate/*` branches and the branch can never go green. The update (including `uv.lock`) just piled up on the branch with no PR and no merge. Switch both rules to `automergeType: "pr"` so Renovate opens a PR (which triggers the existing pull_request CI) and auto-merges it once green, consistent with every other update in this repo. Co-Authored-By: Claude Opus 4.8 Claude-Session: https://claude.ai/code/session_01Wenpt8A75nGV57DDqGvnTA --- renovate.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/renovate.json b/renovate.json index fc72bb67..6bd1e1e4 100644 --- a/renovate.json +++ b/renovate.json @@ -8,7 +8,7 @@ "lockFileMaintenance": { "enabled": true, "automerge": true, - "automergeType": "branch" + "automergeType": "pr" }, "packageRules": [ { @@ -18,7 +18,7 @@ "groupName": "major/minor dev dependencies", "groupSlug": "dev-dependencies", "automerge": true, - "automergeType": "branch" + "automergeType": "pr" }, { "matchPackageNames": ["@apify/*", "@crawlee/*", "apify", "apify-client", "apify-shared", "apify-fingerprint-datapoints", "crawlee", "got-scraping"],