fix(renovate): separate majors and automerge non-major updates - #63
Merged
Conversation
group:all sets separateMajorMinor to false, so majors shared a branch with every other update. Remove it and group only the non-major update types into one automergeable pull request, leaving majors ungrouped and review-required. This repository previously automerged nothing: automerge was false at the root and every package rule set it to false. GitHub Actions and the workflow-managed tooling are its only dependencies, so those rules disabled automatic merging entirely. Also drop dependencyDashboardApproval from the major rule, which suppressed pull-request creation rather than merely requiring review, and adopt pinDigests, statusCheckWhen and the shared concurrency settings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
group:allsetsseparateMajorMinor: false, so majors shared a branch with every other update. Combined withautomerge: falseon major updates, a single eligible major would placeautomerge: falseon the one branch carrying all routine updates.That was academic here until now, because this repository automerged nothing:
automergewasfalseat the root and every package rule set it tofalseas well. Since GitHub Actions and the workflow-managed tooling are the only dependencies this repository has, those two rules disabled automatic merging entirely.Change
group:all. It cannot be kept in any form, because the preset itself setsseparateMajorMinor: false.separateMajorMinorandseparateMultipleMajor, so a multi-version major jump arrives one step at a time and each migration guide applies to a diff containing only that release's breaking changes.minor,patch,pin,pinDigest,digest) into one automergeable pull request.groupName, deliberately: majors are already ungrouped because the bundle matches non-major types only, and forcing one would split lockstep groups whose members must move together.dependencyDashboardApproval: truefrom the major rule. It suppressed pull-request creation entirely, so majors were invisible rather than merely review-required. Majors now open a pull request, labelled, withautomerge: false.pinDigests,statusCheckWhen, unlimited concurrency, explicitdependencyDashboardApproval: false.The custom managers for commitlint and the Tessl CLI are unchanged.
Gate
Non-major updates now merge unattended behind
validate,Skill Review,Commitlint, andtessl-dry-run. A bad Actions or tooling bump fails those. Majors remain a human decision.Note: this repository has no dependency manifest of any kind, so line coverage is not a meaningful gate here; the eval suite is.
Config validated with
renovate-config-validator.