Enable Microsoft Store distribution (lift the MSIX publish pause) #1375

Activity

1. github-project-automation

   added this to Windows Companion Appon Sep 8, 2026
2. github-project-automation

   moved this to Backlog in Windows Companion Appon Sep 8, 2026
3. clawsweeper

   added

   P2Normal priority bug or improvement with limited blast radius.Normal priority bug or improvement with limited blast radius.

   clawsweeper:needs-maintainer-reviewClawSweeper marked this issue as needing maintainer review before automation.ClawSweeper marked this issue as needing maintainer review before automation.

   clawsweeper:needs-product-decisionClawSweeper marked this issue as needing a product or behavior decision.ClawSweeper marked this issue as needing a product or behavior decision.

   clawsweeper:no-new-fix-prClawSweeper does not recommend queueing a new automated fix PR for this issue.ClawSweeper does not recommend queueing a new automated fix PR for this issue.

   issue-rating: 🌊 off-meta tidepoolIssue quality rating does not apply to this item.Issue quality rating does not apply to this item.

   on Sep 8, 2026
4. clawsweeper commented on Sep 8, 2026

   

   clawsweeperbot

   on Sep 8, 2026 – with ClawSweeper

   More actions

   Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed September 8, 2026, 7:17 PM ET / 23:17 UTC.

   Summary
   Store distribution remains deliberately disabled on current main and absent from the latest release. This issue tracks a distinct rollout decision that the open packaging PR explicitly defers.

   Likely related people: shanselman and kmahone are suggested routing candidates for release policy and ARM64 packaging, respectively; routing confidence is low.

   Reproducibility: not applicable. as a bug reproduction: source, tests, and release assets confirm an intentional publishing pause, and the request is to approve a new distribution channel.

   Ways to help us reproduce this

   • Add expected vs actual behavior.

   Maintainer decision needed

   Question	Recommendation
   Should Store distribution remain deferred, become an additional supported channel, or eventually replace EXE distribution?	Retain the pause pending readiness: Keep this rollout tracker open while packaging, consent, ARM64, signed-upgrade evidence, and coexistence acceptance are completed.

   Why: Current policy intentionally pauses MSIX, and neither packaging tooling nor this issue establishes approval to change release channels or their long-term support obligations.

   Next step
   A release owner must choose the channel strategy and acceptance gates before implementation; this is not a safe automatic bug-fix task.

   Review details

   Best possible solution:

   Keep publishing paused until an approved Store channel has validated packaged permissions and signed install/upgrade behavior, with coordinated CI, release-contract tests, documentation, and coexistence safeguards.

   Do we have a high-confidence way to reproduce the issue?

   Not applicable as a bug reproduction: source, tests, and release assets confirm an intentional publishing pause, and the request is to approve a new distribution channel.

   Is this the best way to solve the issue?

   Yes, separating rollout approval from packaging tooling is appropriate. Implementation must also update the enforced release contracts and establish the Store submission path rather than only enabling the build job.

   AGENTS.md: found and applied where relevant.

   Remaining risk / open question:

   • Packaged camera, microphone and location consent, native ARM64 launch, and signed clean-install/upgrade acceptance remain explicitly unverified in the supplied rollout evidence.
   • The permanent relationship between Store and EXE channels is undecided; coexistence behavior is tracked separately and must inform rollout acceptance.
   • Partner Center readiness and the final Store submission path are not established by the disabled CI artifact-build job.

   Codex review notes: model internal, reasoning medium; reviewed against 857fa9c5ffd5.

   Label changes

   Label changes:

   • add P2: This is a concrete distribution improvement with explicit readiness gates; existing EXE and ZIP distribution remains available.
   • add issue-rating: 🌊 off-meta tidepool: Current issue advisory state selects this label.
   • add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
   • add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
   • add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

   Label justifications:

   • P2: This is a concrete distribution improvement with explicit readiness gates; existing EXE and ZIP distribution remains available.

   Evidence reviewed

   What I checked:

   • Verified checkout and policy: The origin URL verifies the target repository; HEAD matches the supplied main revision. Read the complete root AGENTS.md and applied release-proof guidance. No code was changed or build/test commands executed during this read-only review. (AGENTS.md:1, 857fa9c5ffd5)
   • Distribution remains paused on main: The MSIX job has an unconditional false condition, remains continue-on-error, and uploads build artifacts only. The CI gate does not require it, and the release asset list contains only EXE installers and ZIPs. Flipping the condition alone would not establish Store distribution. (.github/workflows/ci.yml:811, 857fa9c5ffd5)
   • Release policy explicitly gates enablement: The release guide requires packaged camera/microphone consent validation and release coverage before resuming MSIX. Its checklist also searches for the pause text. The issue additionally requests location, native ARM64, and signed clean-install/upgrade evidence. (docs/RELEASING.md:154, 857fa9c5ffd5)
   • Tests enforce the current policy: ReleaseWorkflow_PausesMsixDistribution asserts the exact disabled condition, excludes MSIX download/signing steps, and rejects MSIX release assets. An approved rollout must update these contracts alongside workflow and documentation changes. (tests/OpenClaw.Tray.Tests/ReleaseSigningWorkflowTests.cs:118, 857fa9c5ffd5)
   • Latest release has no MSIX asset: GitHub reports v2026.7.1-4 published on 2026-09-03 with four assets: x64 and ARM64 EXE installers plus x64 and ARM64 portable ZIPs.
   • Packaging and coexistence are separate work: The supplied discussion and a REST status check confirm feat: add Microsoft Store MSIX packaging #1328 remains open and draft, explicitly leaving distribution paused. Migrate from the Inno (.exe) app to the Store MSIX #1374 separately tracks coexistence. Four prepared screenshots were inspected: they show duplicate startup/Start entries and packaged startup toggling, supporting useful packaging progress without establishing consent, ARM64, or signed-upgrade readiness.

   Likely related people:

   • shanselman: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)
   • kmahone: Suggested for follow-up; no historical authorship or introduction is verified. (role: unverified routing candidate; confidence: low)

   How this review workflow works

   • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
   • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
   • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
   • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
   • Maintainers can also comment @clawsweeper review to request a fresh review only.
   • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
   • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
   • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.
5. natalie-aguinaldo

   added a commit that references this issue on Sep 11, 2026

   ci: drop the stale MSIX manifest patch step

   ...

   0b2860b
6. karkarl

   added a commit that references this issue on Sep 12, 2026

   feat: add Microsoft Store MSIX packaging (#1328)

   ...

   bd9ce43
7. github-actions commented on Sep 23, 2026

   

   github-actionsbot

   on Sep 23, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue has been automatically marked as stale due to inactivity.
   Please add updated OpenClaw Windows details or it will be closed.
8. github-actions

   added

   stale

   on Sep 23, 2026
9. natalie-aguinaldo commented on Sep 23, 2026

   

   natalie-aguinaldo

   on Sep 23, 2026

   ContributorAuthor

   More actions

   Closed with #1453
10. natalie-aguinaldo

    closed this as completedon Sep 23, 2026
11. github-actions

    locked as resolved and limited conversation to collaborators on Sep 26, 2026