chore(packaging): retire the Microsoft Store channel - #173
Merged
Conversation
The listing reached certification and was unpublished. Packaging was never the problem: the submission API accepts only a Microsoft Entra application, an Entra application needs a tenant, and a Partner Center account opened with a personal Microsoft account has none. Every free route to creating one now ends in a paid Microsoft 365 signup, and submitting by hand every release was not acceptable. tag-release no longer calls publish-msix. The workflow itself is left intact and reachable through workflow_dispatch — it is waiting on an account, not on a fix — and verify-packaging keeps calling it with publish: false so the package is still proven to pack on Windows. packaging/README.md records the dead ends so this does not get re-litigated from scratch. A listing frozen at one version would have been worse than none: an MSIX lives under C:\Program Files\WindowsApps, so classify_install reports it as externally updated and the in-app updater never offers those users anything.
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
1 participant
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 Store listing reached certification and has been unpublished.
Packaging was never the problem — the package built, bundled, certified and installed. Authentication was. The submission API accepts only a Microsoft Entra application, an Entra application needs a tenant, and a Partner Center account opened with a personal Microsoft account has none. Every free route to creating one dead-ends:
That left a card, a manual upload per release, or dropping the channel. The channel was dropped.
What changes
tag-release.ymlno longer callspublish-msix.yml.publish-msix.ymlis left intact and reachable throughworkflow_dispatch. Nothing in it is wrong; it is waiting on an account.verify-packaging.ymlstill calls it withpublish: false, so the MSIX is still proven to pack on Windows.packaging/README.mdrecords the dead ends, the Store ID, and the exact steps to revive the channel.MSSTORE_PRODUCT_IDand the secretSELLER_IDwere deleted.MSIX_IDENTITY_NAME/MSIX_PUBLISHER/MSIX_PUBLISHER_DISPLAY_NAMEstay — the packing step needs them.Why not leave the listing up
An MSIX installs under
C:\Program Files\WindowsApps, which is unwritable, soclassify_installreports it as externally updated and the in-app updater deliberately does nothing (src-tauri/src/lib.rs:125). Store users would have been stranded on 0.28.0 with no update path and no notification. A frozen listing is worse than no listing.The listing assets in
packaging/msix/store-listing/are kept, marked as unused.