Repository navigation
feat: centralize approved Windows Store production and beta flights - #48
Merged
Merged
Conversation
This was referenced Oct 27, 2026
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.
Problem
Gateway and Companion need a central Microsoft Store submission workflow with release-manager approval. Gateway beta delivery must reach the Store Development flight, not stop at a GitHub prerelease.
Outcome
openclaw/releasesthe sole Store submission owner: stable Gateway and Companion targetproduction; Gateway betas targetdevelopment.microsoft-store-gateway; Companion uses its own environment. Check the actual reviewer team, exact-main deployment policy, and no administrator deployment bypass before credentials.flightPackages, preserving flight settings and foreign production drafts. Retain uncertain-commit safeguards and the modern Blob upload protocol fix.The scope correction removes both unapplied branch-ruleset templates and the CODEOWNERS delta. It also corrects the runbook and diagnostics: main-branch ancestry is not proof of code review. Source authorization, environment approval, Store identities, and submission logic are unchanged by this correction.
Coordinated Stack and Rollout
Evidence-writer #47 is closed and is not a dependency. Existing branch protection is retained; no branch-rule changes are required by this rollout.
Merge does not activate beta flight delivery. Configure central
MSSTORE_GATEWAY_DEVELOPMENT_FLIGHT_IDandMSSTORE_GATEWAY_DEVELOPMENT_ENABLED; retire native Gateway activation flags. Keep automation disabled until an explicitly approved manual central submission, certification, and data-preserving tester upgrade are qualified. No new PAT, Store client secret, per-flight environment, or extra federation is required.Administrator runbook.
Validation
Published scope correction:
5057643a39181fedacdeec812aeac1ba0aff9f15. The hosted commit has a valid GitHub signature, preserves the previous head as its parent, and exactly matches the locally tested candidate tree.Rerun on the corrected source:
main, stable/beta separation, current-attempt witness, activation pause, flight drift, and substituted bytes.The previous full-PR independent review was clean at
1fea8b67e111e839b1e9e2f4d46d0bbc30dba6d4; it is not a fresh review of this correction. New-head hosted CI/review are separate from the local checks above.Risk and Remaining Proof
Repository writers remain trusted to change publisher code. Environment approval gates this workflow's credential-bearing job; it does not enforce PR review or guarantee release-manager review of code changes.
No live Store request/approval/submission, package signing, release dispatch, certification, tester upgrade, or GitHub/Entra/Partner Center setting change was performed. Environment/cloud cutover and live flight qualification remain administrator-controlled prerequisites. Local fixtures do not establish live delivery or merge readiness.
Coordinated Store Approval Rollout
These PRs do not change live settings, merge themselves, or authorize a Store submission.