Conversation
…es to release branch Old rule was too conservative: "only milestone on explicit signal, never create milestones, never infer." Result: minor-bump PRs (like #3051 for 3.1.0) shipped unmilestoned and had to be edited manually. New rule: the changeset bump level is explicit signal. Fetch open milestones + patch branches via gh api, then apply the routing matrix — major → next-major milestone on main; minor → next-minor milestone (e.g. 3.1.0) on main; patch → patch milestone on X.Y.x branch (flag-for-human if no patch branch exists); --empty → no milestone, main. Still never creates milestones — if the expected one is missing, flag-for-human. Matches the repo invariant: milestones are a human planning surface, branches are a human release-cut decision. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Two related routing rules added to `triage-prompt.md`:
The routine still never creates milestones — if the expected one is missing, surface the gap and flag for human.
Motivation
Caught on #3051 tonight (vast_tracker / daast_tracker for #2915) — a `minor` changeset that shipped unmilestoned and I had to `gh pr edit --milestone` manually. Also surfaced that no `3.0.x` patch branch is open yet, so any patch triage right now flags for human.
Sibling repos
Not propagating — sibling SDK repos use release-please with their own repo-specific rules. The adcp protocol repo is the one where the milestone/branch mapping matters.
Test plan
🤖 Generated with Claude Code