ci: auto-merge safe Dependabot PRs and group them#54
Merged
Conversation
"Allow auto-merge" was already on for the repo and main already requires status checks, but nothing ever turned auto-merge ON for a given PR, so Dependabot PRs just piled up (13 of them). - New dependabot-auto-merge workflow: enables auto-merge on patch and minor updates, so they merge themselves once the required checks pass. A MAJOR bump (a compiler, a linter, a runtime) is left open for a human, with a comment saying so. - dependabot.yml now groups patch and minor updates into one PR per ecosystem instead of one PR per package, which is what caused the pile-up. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Chineme123
enabled auto-merge
July 14, 2026 21:15
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.
Summary
Fixes the reason 13 Dependabot PRs piled up. "Allow auto-merge" was already enabled on the repo and
mainalready requires status checks, but nothing ever turned auto-merge on for a given PR — that step was missing.dependabot-auto-merge.yml: enables auto-merge on patch and minor updates, so they merge themselves once the required checks pass (build-and-test,frontend,commitlint,codeqlx2). A major bump is deliberately left open for a human and gets a comment explaining why.dependabot.ymlnow groups patch and minor updates into one PR per ecosystem instead of one PR per package, which is what caused the pile-up in the first place.Security note: the workflow uses
pull_request_target(needed for write permissions on Dependabot PRs) but never checks out the PR branch, so an untrusted dependency update cannot execute anything.Linked spec / use case
n/a — repo hygiene (spec 0002 phase 7 governance follow-through).
How it was verified
Existing branch protection already requires the 5 checks, and
allow_auto_mergeis already true on the repo, so the workflow has everything it needs. It will be exercised by the next Dependabot run.Definition of done (from CLAUDE.md)
context/progress-log.mdentry added — deliberately left out of this PR so it cannot conflict with the landing PR (feat(landing): public marketing landing page with prerender, motion and code split (spec 0003) #53), which also edits the log. Added in a follow-up once both land.