Repository navigation
fix(labels): keep Release Please's lifecycle labels on agent-plugins - #945
Conversation
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 <noreply@anthropic.com>
@coderabbitai full review |
Action performed
|
|
No actionable comments were generated in the recent review. Walkthrough
Severity of issue fixed: Medium Merge Risk:
|
Code coverage overviewLanguages: C#, Go C# / code-coverage/dotnet
Go / code-coverage/go
ℹ️ Calculations represent line coverage. Results may change as calculations are updated. Updated |
Readiness at
|
Why
The agent-plugins 3.0.0 release was merged but never tagged. Our label management deletes the label Release Please uses to recognise a merged release, so it lost track of 3.0.0 and proposed a bogus 4.0.0 that re-lists the whole history.
What
Declares Release Please's two lifecycle labels for agent-plugins, so label management keeps them instead of deleting them.
Fixes #944
👉 After merge: relabel agent-plugins#710 as pending so 3.0.0 is tagged. The agent does this.