chore(renovate): automerge minor updates #454

Merged

grachevko merged 1 commit from chore/renovate-automerge-minor into main

2026-10-27 16:28:06 +00:00

hermes commented

2026-10-27 15:02:23 +00:00

Collaborator

What was wrong

Renovate automerged digest and patch updates only, so a minor request sat until the owner merged
it by hand even with Flate - Success and LLM Review - Success green: #452 and #453 carry the
footer Automerge: Disabled by config. Please merge this manually once you are satisfied.

What this fixes

.renovaterc.json5: minor joins the automerge rule. The minimumReleaseAge: "1 day" quarantine
stays, so a release still has to be a day old before it can merge itself.
AGENTS.md: the Contributing paragraph now says digest, patch and minor merge themselves, while a
major update waits for the owner.

Verified

git diff --stat: two files, 5 lines, no other file touched.
git grep -i automerge: no other text in the repository states the old digest/patch scope.
The gate this relies on is live: GET /repos/grachevko/home-ops/branches/main answers
enable_status_check: true with contexts Flate - Success* and LLM Review - Success*, so a
platform automerge waits for CI instead of merging seconds after the pull request opens.

After the merge

Nothing to apply: the file is read by the next Renovate run (cron 03:00 UTC). Whether that run
arms automerge on the already open #452 and #453 is not proven — those bodies were written under
the old scope.

Rollback

Revert the commit: minor requests go back to waiting for the owner.

## What was wrong - Renovate automerged digest and patch updates only, so a minor request sat until the owner merged it by hand even with `Flate - Success` and `LLM Review - Success` green: #452 and #453 carry the footer `Automerge: Disabled by config. Please merge this manually once you are satisfied.` ## What this fixes - `.renovaterc.json5`: `minor` joins the automerge rule. The `minimumReleaseAge: "1 day"` quarantine stays, so a release still has to be a day old before it can merge itself. - `AGENTS.md`: the Contributing paragraph now says digest, patch and minor merge themselves, while a major update waits for the owner. ## Verified - `git diff --stat`: two files, 5 lines, no other file touched. - `git grep -i automerge`: no other text in the repository states the old digest/patch scope. - The gate this relies on is live: `GET /repos/grachevko/home-ops/branches/main` answers `enable_status_check: true` with contexts `Flate - Success*` and `LLM Review - Success*`, so a platform automerge waits for CI instead of merging seconds after the pull request opens. ## After the merge - Nothing to apply: the file is read by the next Renovate run (cron 03:00 UTC). Whether that run arms automerge on the already open #452 and #453 is not proven — those bodies were written under the old scope. ## Rollback - Revert the commit: minor requests go back to waiting for the owner.

hermes added 1 commit

2026-10-27 15:02:23 +00:00

chore(renovate): automerge minor updates

Flate / Flate - Filter (pull_request) Successful in 4s

Details

Flate / Flate (pull_request) Has been skipped

Details

Flate / Flate - Success (pull_request) Successful in 3s

Details

LLM Review / LLM Review (pull_request) Successful in 16m34s

Details

LLM Review / LLM Review - Success (pull_request) Successful in 4s

Details

5a8b9a9d65

## What was wrong

- Renovate automerged digest and patch updates only, so a minor request sat until the owner merged
  it by hand even with `Flate - Success` and `LLM Review - Success` green: #452 and #453 carry the
  footer `Automerge: Disabled by config. Please merge this manually once you are satisfied.`

## What this fixes

- `.renovaterc.json5`: `minor` joins the automerge rule. The `minimumReleaseAge: "1 day"` quarantine
  stays, so a release still has to be a day old before it can merge itself.
- `AGENTS.md`: the Contributing paragraph now says digest, patch and minor merge themselves, while a
  major update waits for the owner.

## Verified

- `git diff --stat`: two files, 5 lines, no other file touched.
- `git grep -i automerge`: no other text in the repository states the old digest/patch scope.
- The gate this relies on is live: `GET /repos/grachevko/home-ops/branches/main` answers
  `enable_status_check: true` with contexts `Flate - Success*` and `LLM Review - Success*`, so a
  platform automerge waits for CI instead of merging seconds after the pull request opens.

## After the merge

- Nothing to apply: the file is read by the next Renovate run (cron 03:00 UTC). Whether that run
  arms automerge on the already open #452 and #453 is not proven — those bodies were written under
  the old scope.

## Rollback

- Revert the commit: minor requests go back to waiting for the owner.

pr-agent commented

2026-10-27 15:03:33 +00:00

Collaborator

Failed to update PR description

pr-agent commented

2026-10-27 15:03:48 +00:00

Collaborator

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

## PR Reviewer Guide 🔍 Here are some key observations to aid the review process: <table> <tr><td>⏱️ <strong>Estimated effort to review</strong>: 1 🔵⚪⚪⚪⚪</td></tr> <tr><td>🧪 <strong>No relevant tests</strong></td></tr> <tr><td>🔒 <strong>No security concerns identified</strong></td></tr> <tr><td>⚡ <strong>No major issues detected</strong></td></tr> </table>

pr-agent commented

2026-10-27 15:04:06 +00:00

Collaborator