The un-namespaced `backport` and `backport-previous` were accepted
alongside `kind/backport` and `kind/backport-previous` so that the rename
could land in any order relative to the org-level dosubot, which was
then the dominant applier on real backports. Both conditions for
dropping them now hold: dosubot no longer labels PRs here -- every
backport label applied in the last month came from a maintainer -- and
.github/labels.yml has renamed the labels themselves, so neither legacy
name exists in the repository and the picker offers only the namespaced
pair.
Three sites went together, because a half-finished rename is worse than
either end of it: the concurrency group key, `prepare`'s `if:` gate, and
the `Check which labels are present` step. A name dropped from one and
not the others either routes a genuine request into a group it must
queue behind, or qualifies a run that then finds no target.
The aliases stay in .github/labels.yml on purpose. An alias is not a
label, so nothing offers a legacy name; what it does is make the next
label sync rename a stray back into kind/*, carrying its PRs with it,
rather than leaving a dead label that triggers nothing and that nothing
ever cleans up. That sync is weekly, which docs/release.md now states
alongside the accepted spellings.
Assisted-By: LLM
Signed-off-by: Myasnikov Daniil <myasnikovdaniil2001@gmail.com>
Myasnikov Daniil
900fc0e2e5