Fix beta release safety and packaging - #1
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.
What changed
1.2.1-beta4and refreshes the questionnaire, instructions, build status, and package metadata.Why
The beta3 GitHub release exposed only the installer even though the documentation promised four downloads. Review also found a first-launch multi-selection race, optional archive verification, ambiguous failed-copy output, and incorrect storage classification.
User impact
Testers receive a complete four-file beta package. Explorer multi-selections are retained during first launch, archives cannot be published without verification, failed copies are cleaned up conservatively, and copy concurrency is safer on HDDs.
Validation
162609476CB264F969AF0DDD99F8E71954B4659CF5504AAA08A464F5B86B7022