Skip to content

chore(deps): bump debian from 4e401d9 to 020c0d2 - #59

Merged
SilverKnightKMA merged 3 commits into
mainfrom
dependabot/docker/debian-020c0d2
Jul 20, 2026
Merged

SilverKnightKMA merged 3 commits into
mainfrom
dependabot/docker/debian-020c0d2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 18, 2026

Copy link
Copy Markdown
Contributor

Bumps debian from 4e401d9 to 020c0d2.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps debian from `4e401d9` to `020c0d2`.

---
updated-dependencies:
- dependency-name: debian
  dependency-version: 13-slim
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@SilverKnightKMA
SilverKnightKMA merged commit a579606 into main Jul 20, 2026
8 checks passed
@SilverKnightKMA
SilverKnightKMA deleted the dependabot/docker/debian-020c0d2 branch July 20, 2026 04:19
SilverKnightKMA added a commit that referenced this pull request Jul 20, 2026
)

PR #64 misdiagnosed the lingering branch as a side effect of reusing a
fixed branch name. The real cause is a long-standing GitHub platform
bug (orgs/community#63409): when a PR is merged via a bot/App token
(actor: github-actions[bot]), the repo setting delete_branch_on_merge
is silently ignored. User-merged PRs on the same repo delete fine.

Evidence from this repo's timeline:
- PRs #44, #45, #47, #55, #62 (merged_by=github-actions[bot]): no
  auto-delete; branches lingered until manually removed.
- PRs #58, #59, #60 (merged_by=SilverKnightKMA): auto-deleted within
  1 second of merge.

Renaming the branch per run (PR #64) only stops branch reuse; it does
not delete the merged branch. Without this workflow, merged branches
would accumulate indefinitely one per week.

This workflow explicitly deletes the head branch on PR close (merged),
scoped to same-repo automation branches (automated/*, dependabot/*,
deps/*, chore/*) or trusted bot authors. Fork branches are skipped and
deletion is idempotent.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant