Repository navigation
Conversation
Dependabot PR #5 (setup-python 6 -> 7) never ran the test job: at its base, the Release workflow had no pull_request path for its own file, so only Actions Maintenance ran, and it failed approving the PR. This branch carries the identical one-line change on top of current main, where docker-release.yml triggers on its own path. The Release workflow therefore runs pytest on setup-python v7 plus the three e2e round trips, exactly as #5 will after a Dependabot rebase. v7.0.0 only drops the pip-install input, which no workflow here uses; the action runtime stays node24. Canary only, not meant to be merged: #5 is the PR to merge.
Contributor
Author
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 for #5, do not merge
This is the same one-line change as Dependabot PR #5 (
actions/setup-pythonv6 -> v7 in the🧪 Pytestjob), placed on top of currentmain. It shows what #5 will report after@dependabot rebase. Merge #5, not this PR. Close this one once #5 is in.Why #5 is red: not setup-python v7
The only failing check on #5 is
Auto-merge Dependabot PRs / Docker Maintenance(run 30191230634, 2026-07-26). It failed in the auto-approve step:Two things caused that, and both are already fixed:
automation-templates@e5fbd2b) approved every Dependabot PR without any condition. Since fix(docker-maintenance): guarded Dependabot auto-merge behind CI automation-templates#113 (fe9edd8, 2026-10-08), a merge guard leaves semver-major updates open and keeps the job green. Canary canary: dmdguard major (do not merge) #10 (major) loggedDecision: ok=false reason=majorand passed.can_approve_pull_request_reviews: true, and canary canary: dmdguard minor with required checks (do not merge) #9 created an approving review on 2026-10-08.setup-python v7 itself never ran on #5. At #5's base (
441ac72), thepull_requestpaths ofdocker-release.ymldid not include the workflow file. That path was added on main in6d1d80b(2026-10-09).v7.0.0 release notes (fetched 2026-10-09)
action.ymlchange from v6 to v7 is that thepip-installinput is gone. No workflow here uses it.node24.Expected checks
🧪 Pytest(on setup-python v7),🧪 E2E Round Trip (compose|lts|latest), the validations and🔨 Validate backuphelper Build (PR)all go green.Auto-merge Dependabot PRsis skipped here, because the actor is not Dependabot.