ci: auto-merge Dependabot patch and minor updates - #31
Merged
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.
What
Adds
.github/workflows/dependabot-automerge.yml— a semver-aware Dependabot auto-merge workflow.How
dependabot[bot]only.--squashto match the squash-only, linear-historymainruleset.on: pull_requestmerge-race while required checks are still queued.contents: write+pull-requests: write).fetch-metadataSHA-pinned to v3.1.0, matching the repo's actions-pinning policy.Why safe
The active
mainruleset requires 5 status checks (backend build + contract drift, frontend verify + build, mutation gate 80, Bruno E2E, Playwright E2E), so--autogenuinely waits for CI before merging. Grouped Dependabot PRs containing a major bump reportupdate-type: majorand correctly stay manual.