Repository navigation
Preserve draft releases when GitHub returns a stale release list - #10
Merged
Merged
Conversation
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 v0.0.4 publisher created its draft successfully, then failed with
Draft release was not retained.because GitHub's release list did not yet contain it. Publication now uses the creation response immediately. Subsequent lookups fetch release details by ID, falling back to GitHub's pending-tag lookup when a draft is missing from the list, so retries reuse the existing draft and its files. API errors still stop publication.Regression tests cover stale lists during creation and recovery, and failed direct lookups. Add the standard
Covered::Susintegration for reproducible coverage checks.Validation:
COVERAGE=PartialSummary bundle exec sus-parallel: 44 tests, 126 assertions; every changed publisher line covered.The original v0.0.4 files have been verified and restored to its existing draft. The original publishing run can resume without rebuilding or preparing another version.