Summary
The renovate.json template currently auto-merges only patch, pin, and digest updates:
{
"description": "Auto-merge patch / pin / digest bumps once CI passes",
"matchUpdateTypes": ["patch", "pin", "digest"],
"automerge": true
}
Consider broadening this to also include minor so that minor crate bumps auto-merge once CI passes.
Motivation
In consumer repos (e.g. rvpm) minor Renovate PRs pile up and require manual merging even though CI is green. Broadening the rule to minor reduces this maintenance load.
Prerequisite for consumer repos
For auto-merge to actually fire, the consumer repo needs:
allow_auto_merge: true at the repo level (GitHub setting)
- Branch protection on
main with required status checks
These are set up at the consumer-repo level (e.g. rvpm now has both), not in the template. The template change is just to opt minor bumps into automerge — it won't have any effect on repos that haven't met the prerequisites above.
Caveat: 0.x crates
For pre-1.0 Rust crates (e.g. reqwest 0.13.x), a SemVer "minor" bump is effectively breaking. Two options:
- Accept the risk (CI catches most regressions).
- Add an exclusion rule for crates whose current version starts with
0. so they stay manual.
The simpler option is fine if CI coverage is solid; otherwise the exclusion is worth adding.
Proposed change
{
"description": "Auto-merge minor / patch / pin / digest bumps once CI passes",
"matchUpdateTypes": ["minor", "patch", "pin", "digest"],
"automerge": true
}
Context
Originally tried to apply this directly in rvpm, but renovate.json is kata-managed from this template — local edits would be reverted on the next kata apply. Filing here so the change can be made at the source.
Summary
The
renovate.jsontemplate currently auto-merges onlypatch,pin, anddigestupdates:{ "description": "Auto-merge patch / pin / digest bumps once CI passes", "matchUpdateTypes": ["patch", "pin", "digest"], "automerge": true }Consider broadening this to also include
minorso that minor crate bumps auto-merge once CI passes.Motivation
In consumer repos (e.g.
rvpm) minor Renovate PRs pile up and require manual merging even though CI is green. Broadening the rule tominorreduces this maintenance load.Prerequisite for consumer repos
For auto-merge to actually fire, the consumer repo needs:
allow_auto_merge: trueat the repo level (GitHub setting)mainwith required status checksThese are set up at the consumer-repo level (e.g.
rvpmnow has both), not in the template. The template change is just to opt minor bumps into automerge — it won't have any effect on repos that haven't met the prerequisites above.Caveat: 0.x crates
For pre-1.0 Rust crates (e.g.
reqwest0.13.x), a SemVer "minor" bump is effectively breaking. Two options:0.so they stay manual.The simpler option is fine if CI coverage is solid; otherwise the exclusion is worth adding.
Proposed change
{ "description": "Auto-merge minor / patch / pin / digest bumps once CI passes", "matchUpdateTypes": ["minor", "patch", "pin", "digest"], "automerge": true }Context
Originally tried to apply this directly in
rvpm, butrenovate.jsonis kata-managed from this template — local edits would be reverted on the nextkata apply. Filing here so the change can be made at the source.