Repository navigation
Clarify local Hub rehearsal and record native publisher UI acceptance - #375
Merged
Merged
Conversation
Contributor
Author
|
Local CI passed on dd74d9b ( GitHub would run for this PR: desktop.yml. Merged on this local pass (macOS runner queue); GitHub CI runs on the merge commit on main.
Notes:
|
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 desktop rehearsal guide now makes the optional local legacy test catalog explicit, uses quoted paths and isolated app data, and points ordinary developer publishing to the GitHub workflow and App Hub submission issue. The recipe was checked against current source; its newly written commands are not claimed as a fresh end-to-end execution.
Adds bilingual, source-bound evidence from actual native publishing UI checks: macOS source5607 and the final packaged5e1 each passed8/8; OnePlus source8af passed8/8 functional checks. Genuine GitHub-proven fixture releases were installed through isolated temporary legacy catalogs. These results are separate from productionv2 catalog verification and from acceptance of the actual ymote sample apps.
Original screenshots and sanitized receipts are included. The phone’s long fixture title clips at the right edge, explicitly recorded as a visual defect rather than a clean mobile UX pass. No private paths, accounts, credentials or raw logs are included. JSON/relative links, screenshot hashes and diff checks pass.
Keep this PR stacked until the compatible host release PR370 finishes; it does not change the frozen host/runtime candidate.