Repository navigation
Keep delayed Draft jobs from blocking Ready checks - #13
Merged
Merged
Conversation
silveltman
marked this pull request as ready for review
October 14, 2026 18:54
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.
A delayed Draft job can have a higher check-run ID than the newer Ready workflow. This made Ready wait on a skipped Draft result even after the real Ready check succeeded.
Compare the originating workflow run before job ID, while retaining the latest attempt within a run. New pending, failed, or skipped Ready checks still block publication.
Validation: 23 workflow tests pass, including the actual delayed-Draft IDs and newer failed Ready runs. Caller concurrency will separately isolate Draft and Ready to prevent cancellation.