Skip to content

ci: unify the Dependabot auto-merge workflow across all repositories #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
markuslf merged 1 commit into from
Aug 3, 2026
Merged

ci: unify the Dependabot auto-merge workflow across all repositories #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 13 additions & 12 deletions .github/workflows/dependabot-auto-merge.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,10 +6,11 @@ on:
permissions: 'read-all'

env:
# Lockfiles that have no `directory:` entry in `.github/dependabot.yml`
# because upstream packages keep raising their minimum Python. Dependabot
# security updates ignore that allowlist, so a bump can still show up here.
FROZEN_LOCKFILES: '["/lockfiles/py39", "/lockfiles/py310"]'
# Lockfile directories pinned to versions that still support an old
# interpreter. They have no `directory:` entry in `.github/dependabot.yml`,
# but Dependabot security updates ignore that allowlist, so a bump against
# one can still show up here. Empty in repositories without lockfiles.
FROZEN_LOCKFILES: '[]'

jobs:
auto-merge:
Expand All @@ -28,8 +29,8 @@ jobs:
# drops the interpreter the lockfile exists for (py39 -> RHEL 8, RHEL 9,
# Debian 11; py310 -> Ubuntu 22.04). It may equally propose a security
# fix that still supports it. Only a human can tell the two apart, so
# the PR is neither merged nor closed. Regenerate the lockfile with
# `pip-compile` on a matching Python host once the bump is accepted.
# the pull request is neither merged nor closed. Regenerate the lockfile
# with `pip-compile` on a matching Python host once the bump is accepted.
- if: >-
contains(fromJSON(env.FROZEN_LOCKFILES), steps.meta.outputs.directory)
&& github.event.action == 'opened'
Expand All @@ -41,16 +42,16 @@ jobs:
GH_TOKEN: '${{ secrets.GITHUB_TOKEN }}'
PR_URL: '${{ github.event.pull_request.html_url }}'

# `gh pr merge --auto` is refused while the pull request sits in clean or
# unstable state, which is exactly where a freshly opened Dependabot pull
# request lands once the required checks pass while the optional ones are
# still running. The direct merge is a safe fallback: branch protection
# keeps enforcing the required checks server-side, so a pull request that
# is not ready is still rejected.
- if: >-
!contains(fromJSON(env.FROZEN_LOCKFILES), steps.meta.outputs.directory)
&& (steps.meta.outputs.update-type == 'version-update:semver-patch'
|| steps.meta.outputs.update-type == 'version-update:semver-minor')
# `gh pr merge --auto` is refused while the pull request sits in clean or
# unstable state, which is exactly where a freshly opened Dependabot pull
# request lands once the required checks pass while the optional ones are
# still running. The direct merge is a safe fallback: branch protection
# keeps enforcing the required checks server-side, so a pull request that
# is not ready is still rejected.
run: |
gh pr merge --auto --squash "$PR_URL" || gh pr merge --squash "$PR_URL"
env:
Expand Down