Repository navigation
Conversation
Marcisbee
marked this pull request as ready for review
October 22, 2026 17:49
Marcisbee
deleted the
kode/EJYFPDI1-add-client-routing-and-route-data-handli-after-64
branch
October 22, 2026 17:56
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
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.
The draft-release job stopped with “Multiple automatic release drafts exist” because a leftover automatic v0.5.0 draft coexisted with the published v0.5.0 release and the current v0.6.0 draft.
Exclude automatic drafts at or below the latest published stable version when selecting the current draft. Leave their contents and all published releases untouched; still reject conflicting future automatic drafts and protect manual drafts.
Validation: reproduced the reported error with the regression case before the change; all three release-script tests now pass, including stale/published preservation and conflicting future drafts. The existing failed workflow was also recovered by retiring the stale draft’s automation marker: attempt 2 succeeded and refreshed the v0.6.0 draft to merged commit b21fe9e. No release was published.