chore: add canonical dependabot-auto-merge workflow (canary)#3
Open
kayodebristol wants to merge 1 commit into
Open
chore: add canonical dependabot-auto-merge workflow (canary)#3kayodebristol wants to merge 1 commit into
kayodebristol wants to merge 1 commit into
Conversation
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.
Canary rollout of the canonical Dependabot Auto-Merge workflow (verbatim copy of
plures/pluresdb/.github/workflows/dependabot-auto-merge.yml, v4).Why: org-wide diagnosis found dependabot PRs piling up unmerged for ~2 months (security-first directive violated).
openclawwas one of the repos MISSING this workflow entirely.Do NOT merge yet — this is the canary for a mechanical fleet sweep. Remaining first-party targets missing the workflow:
fsm,pares-umbra-data. (holepunch/nixpkgs/xstate forks intentionally excluded.)Known follow-up (Bug A, tracked separately): the canonical workflow itself holds GitHub-Actions major bumps + grouped bumps for human review (
direct:production+semver-majorguard misclassifiesgithub_actionsbumps). Fix that in pluresdb first, then this canary + sweep inherit it. See findings doc.