mirror of
https://github.com/spantaleev/matrix-docker-ansible-deploy.git
synced 2026-08-29 20:13:13 +00:00
Automerge patch bumps of components whose role has a Molecule scenario
A component bump touches that role's defaults/main.yml, which is on the Molecule workflow's path filter, so the change-detection job runs that role's scenario. The bump therefore only merges once the new version has actually been started on the configuration the role renders. That is a real gate, and a stronger one than a human reading a version number in a diff. Patch only. A minor carries behaviour changes that no static rule can judge - the MASH fleet tried a minor-automerge preset across 21 stateless roles and reverted all of them, because reading a given release's notes is what decides it, and that is a job for a human or an agent rather than a config file. Branch push rather than a PR, as with the other automerge rules here. The list has to stay in step with the roles that actually have a scenario, so bin/check-molecule-automerge-list.py enforces it from prek. The direction that matters is a role keeping automerge after losing its scenario: bumps would then merge with nothing exercising them. It reports the harmless direction too, since a role gaining a scenario without being listed is usually an oversight. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01SEH3vxYSQ5SV4N5z61eyGT
This commit is contained in:
co-authored by
Claude Opus 5
parent
8e53dbf940
commit
2d258cf0e0
@@ -79,6 +79,24 @@
|
||||
],
|
||||
"automerge": true,
|
||||
"automergeType": "branch"
|
||||
},
|
||||
{
|
||||
"description": "Automerge patch bumps of components whose role has a Molecule scenario (via branch push - no PR). A bump touches that role's defaults/main.yml, which makes the Molecule workflow run that role's scenario, so the update only merges once the component has been started on the configuration the role renders. Patch only: a minor carries behaviour changes no static rule can judge, and reading the release notes to decide is a job for a human or an agent. Keep this list in step with the roles that have a scenario - bin/check-molecule-automerge-list.py enforces that.",
|
||||
"matchFileNames": [
|
||||
"roles/custom/matrix-alertmanager-receiver/defaults/main.yml",
|
||||
"roles/custom/matrix-bot-baibot/defaults/main.yml",
|
||||
"roles/custom/matrix-bot-matrix-reminder-bot/defaults/main.yml",
|
||||
"roles/custom/matrix-bridge-heisenbridge/defaults/main.yml",
|
||||
"roles/custom/matrix-bridge-hookshot/defaults/main.yml",
|
||||
"roles/custom/matrix-bridge-mautrix-discord/defaults/main.yml",
|
||||
"roles/custom/matrix-bridge-mautrix-meta-messenger/defaults/main.yml",
|
||||
"roles/custom/matrix-bridge-mautrix-whatsapp/defaults/main.yml"
|
||||
],
|
||||
"matchUpdateTypes": [
|
||||
"patch"
|
||||
],
|
||||
"automerge": true,
|
||||
"automergeType": "branch"
|
||||
}
|
||||
],
|
||||
"pre-commit": {
|
||||
|
||||
Reference in New Issue
Block a user