From 8e53dbf940ab30273ea2a37c53b0dbcff03499c0 Mon Sep 17 00:00:00 2001 From: Slavi Pantaleev Date: Thu, 27 Aug 2026 17:51:26 +0300 Subject: [PATCH] Automerge Molecule's own dependency updates Anything under molecule-shared/ - the helper container images, Postgres, and the Python pins - is on the Molecule workflow's path filter, and a change to a shared file makes the detect job run every scenario rather than a subset. So an update there is already gated on the whole suite passing on its own branch, which is a stronger check than a human reading the diff. Branch push rather than a PR, matching how the housekeeping updates in this file already work: nothing to review and no email on success, and a failure still surfaces as a PR. This is also how a new Postgres major reaches us. The bump to the pin runs every scenario against it before it can merge, so if a component does not cope with the new major we find out from a failed Renovate branch rather than from a user. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT --- .github/renovate.json | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.github/renovate.json b/.github/renovate.json index 6ee534548..928ce8b76 100644 --- a/.github/renovate.json +++ b/.github/renovate.json @@ -70,6 +70,15 @@ ], "automerge": true, "automergeType": "branch" + }, + { + "description": "Molecule's own dependencies merge via branch push (no PR, no email). Anything under molecule-shared/ - the helper container images, Postgres, and the Python pins - triggers the Molecule workflow, and a change to a shared file makes it run every scenario, so an update only merges once the whole suite has passed on it. A failure surfaces as a PR instead. This is how a new Postgres major reaches us: the bump runs every scenario against it before anything is merged.", + "matchFileNames": [ + "molecule-shared/**", + ".github/workflows/molecule.yml" + ], + "automerge": true, + "automergeType": "branch" } ], "pre-commit": {