Repository navigation
Update release testing for current transports and recovery scenarios - #85
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 release-testing procedure last changed in
0c95139(#77), while current main is6ec1b68(#84). Its baseline installation, trust, routing and recovery checks remain useful, but it omitted existing SOCKS5 and HTTPS HTTP/3 preference modes and did not make recent regression scenarios independently reportable.Update the English and Russian procedures together: preserve all 57 existing scenario IDs, add 22 (79 total per language), and correct transport-dependent UDP expectations. The procedure now includes SOCKS5, whole-chain HTTP/3 fallback and terminal errors, connection-test HTTP/3 probes, TCP DNS, subscription notification/startup races, stale callbacks, storage recovery and socket shutdown. Clarify Fastlane/CI versus signed-device evidence, release merge/tag/VirusTotal verification, and that release automation does not enforce manual acceptance.
Changes since the previous procedure update
d30d064#782e8f651#79369c41f#803f48cc3#8121d045a#82e760b95#836ec1b68#84Two omissions already predated that baseline: #75's optional HTTP/3/Jump fallback is now H12–H15; #76's SOCKS5 is S01–S04. Native HTTP/3 diagnostics in the Test button are now T10, explicitly distinguished from Android TUN/browser traffic.
Validation
0c95139..6ec1b68history/diff with production paths, existing regression tests, device scenarios, Fastlane lanes and release workflows.git diff --checkpassed.