Preserve release artifacts across workflow retries - #8
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
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.
The v0.0.3 upload succeeded, but immediate registry verification failed during propagation. A full workflow rerun then lost the Actions artifact, so the publisher could not restore the original bytes.
Preserve the verified gem, receipt and both attestation bundles as draft GitHub release assets before uploading to RubyGems. Recovery falls back to those assets when the Actions artifact is missing or expired. Publish the draft only after registry verification and tag creation; conflicting assets, source commits and tags still stop the release.
Retry absent registry data for up to one minute. Different gem bytes, conflicting attestations and other registry errors still fail immediately. Update the release guide and generated context to explain recovery and incomplete drafts. Existing runs execute their original code and require manual recovery; this change applies to subsequent releases.
Validation: 42 tests / 115 assertions pass, including a fresh workspace restoring after loss of the Actions artifact, interrupted finalization, failed preservation, incomplete/conflicting backups, and registry propagation. All 68 changed executable lines are covered. RuboCop and documentation coverage pass.