Group dependabot's minor and patch updates; keep majors one PR each - #160
Merged
Merged
Conversation
The config from #150 was right about WHAT to update and wrong about how many PRs to open for it. Its first run opened eight at once. That is expensive here specifically. This repository's ruleset requires a branch to be current before it merges, and its CI runs 30-40 minute mutation shards. So each merge knocked the remaining PRs out of date and restarted all of their CI — eight serial cycles is most of a day of runners for one week's updates, and eight open PRs is the exact backlog the maintainer asked to have cleared. Minor and patch updates now group into one PR per ecosystem. Majors are left ungrouped on purpose: a breaking change needs its own reading, and bundling it beside a set of patch bumps is how it gets approved without one. Of the first eight PRs, six were majors. The config also now says, beside the actions entry, where a green PR is weak evidence — and for two actions, none at all: - setup-oras is used only by deposit-layer.yml, which runs only on workflow_dispatch, so PR CI never executes it; - cosign-installer is exercised on PRs by ci.yml, but its SIGNING use is in release.yml, which runs on a tag. A green PR proves the installer installs, not that `cosign sign-blob` still works. Both surface only at a release or a deposit — the point of no return that v0.34.3 records the cost of — so the note says to exercise those paths deliberately before merging a major. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019TNtfRjLNhEz82G2ggeeNu
avrabe
enabled auto-merge (squash)
September 17, 2026 02:50
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.
#150's first run opened eight PRs at once. On a repo whose ruleset requires a
branch to be current and whose CI runs 30–40 min mutation shards, each merge
knocks the rest out of date and restarts their CI — most of a day of runners per
week, and exactly the open-PR backlog that was just cleared.
majors, and a breaking change bundled beside patch bumps is how it gets
approved unread.
The config now also records where a green PR is weak evidence, and for two
actions none at all:
setup-orasis used only bydeposit-layer.yml, which runs only onworkflow_dispatch— PR CI never executes it.cosign-installer's signing use is inrelease.yml, which runs on a tag.A green PR proves the installer installs, not that
cosign sign-blobworks.Both would surface at a release or deposit — the point of no return v0.34.3
records the cost of.
🤖 Generated with Claude Code