From db51a27c8360124bd9c76ecd0e8e8e92d50550cd Mon Sep 17 00:00:00 2001 From: Nikolai Emil Damm Date: Sun, 15 Nov 2026 01:16:59 +0100 Subject: [PATCH] fix(labels): keep Release Please's lifecycle labels on agent-plugins The authoritative IssueLabels set deleted autorelease: pending minutes after Release Please applied it, so the merged 3.0.0 release PR was never tagged and the next release PR re-proposed the whole history as 4.0.0. Co-Authored-By: Claude Opus 5.5 --- deploy/labels/agent-plugins.yaml | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/deploy/labels/agent-plugins.yaml b/deploy/labels/agent-plugins.yaml index dad71f30..9f8b502a 100644 --- a/deploy/labels/agent-plugins.yaml +++ b/deploy/labels/agent-plugins.yaml @@ -1,8 +1,10 @@ # Issue labels for devantler-tech/agent-plugins. The canonical org taxonomy (15 labels) # is appended to every IssueLabels by the shared patch in kustomization.yaml; this -# file adds only agent-plugins's repo-specific extras (the dependency/ecosystem labels -# Dependabot/Renovate apply), declared so the authoritative set doesn't churn -# against the bots. See ../README.md. +# file adds only agent-plugins's repo-specific extras: the dependency/ecosystem labels +# Dependabot/Renovate apply, and the two lifecycle labels Release Please uses to find +# the release PR it must tag (`autorelease: pending`) and to mark it done +# (`autorelease: tagged`). Declared so the authoritative set neither churns against the +# bots nor deletes release state. See ../README.md. apiVersion: repo.github.m.upbound.io/v1alpha1 kind: IssueLabels metadata: @@ -20,6 +22,10 @@ spec: label: - name: "dependencies" color: "ededed" + - name: "autorelease: pending" + color: "ededed" + - name: "autorelease: tagged" + color: "ededed" providerConfigRef: kind: ProviderConfig name: default