Repository navigation
Submit the Store bundle through the Store submission API when a release is published - #52
Merged
Merged
Conversation
store-submit.yml uploads a release run's msixbundle with the Microsoft Store Developer CLI, sets What's new from the version's CHANGELOG section, and commits it for certification. release.yml calls it after the Windows job on a tag that ships Windows; it can also be run by hand for an earlier run's bundle. Until the PARTNER_CENTER_* secrets exist it skips with a notice. docs/STORE-PLAN.md has the one-time Partner Center setup. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…'s findings - Runs on release: published (and by hand with a tag), not on the tag push, so the Store waits for the same screen reader check the GitHub draft does. It finds the release.yml run that built the tag; release.yml no longer calls it. A release that doesn't ship on Windows is skipped. - msstore publish takes the bundle as its path argument; -i is a directory, so the old call could never upload. - msstore pinned to v0.4.3 (earlier versions wrapped their JSON output) and the setup action to v1.4 (node24). - The submission JSON goes through --payload, not the command line. - Everything that can fail is checked before the upload: the tag, the release run, and the What's new text, which is now the CHANGELOG section from its first ### heading, without links, cut at a whole line. - Exit codes checked after submission get; no listing is an error; inputs reach scripts through env. - STORE-PLAN.md, WORKFLOW.md and CLAUDE.md describe it, including that a submission still in certification blocks the next one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kellylford
changed the title
kellylford
enabled auto-merge (squash)
October 22, 2026 13:54
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.
Kelly asked whether the Store has an API we can use, so updates don't need a manual Partner Center upload. It does: the Store submission API, through Microsoft's Store Developer CLI (
msstore)..github/workflows/store-submit.ymlrssquick-microsoft-storebundle and checks its version.msstore publish … --noCommituploads it into a draft submission.msstore submission publishcommits the draft for certification.release.ymlgains astorejob afterpackage, on tags that ship Windows (secrets: inherit).gh secret set) is indocs/STORE-PLAN.mdunder Submitting through the API.Not yet tried against Partner Center, since the credentials don't exist yet. The docs list
.msixand.msixuploadfor-i. Our file is an.msixbundle, so the first run is where we find out whether it's accepted.🤖 Generated with Claude Code