Recover interrupted draft uploads from a complete release archive - #15
Merged
Merged
Conversation
samuel-williams-shopify
force-pushed
the
preserve-complete-release-backup
branch
2 times, most recently
from
September 21, 2026 21:26
835ae8b to
f72aa5d
Compare
samuel-williams-shopify
force-pushed
the
preserve-complete-release-backup
branch
from
September 21, 2026 21:30
f72aa5d to
dfd76ff
Compare
samuel-williams-shopify
deleted the
preserve-complete-release-backup
branch
September 21, 2026 21:33
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.
Preserve the gem, receipt, and both attestation bundles together in a
release.tarasset before uploading individual release assets. Once that upload completes, a rerun can recover an interrupted draft even when the Actions artifact has disappeared. The archive uses RubyGems' existing tar support without adding a dependency.Recovery verifies the archive digest, accepts only the four expected regular files, and then performs the existing source, package, and attestation checks. Preservation resumes missing uploads and rejects conflicting files or assets. Older complete releases still recover from their individual assets. If neither backup completed, manual restoration remains necessary.
Retains the current release-note extraction and version-only titles. Recovery instructions are maintained in the shared guide and generated agent context.
Validation: the full Sus suite, 100% measured coverage, RuboCop, and API documentation checks pass. Tests cover interrupted uploads with and without Actions artifacts, corrupted/conflicting backups, incomplete legacy drafts, unsafe archive entries, and preservation of release descriptions.