Repository navigation
ci: 🚀 publish releases to the Microsoft Store - #43
Merged
Merged
Conversation
A new store job in release.yml submits the MSIX bundle to the Store with the Microsoft Store CLI. It runs only when the repository variable STORE_AUTO_PUBLISH is 'true', since the CLI can't make a first submission and one still in certification blocks a new one. - Copies the last published submission and swaps in the new bundle - set-release-notes.ps1 sets What's new in every language from listings.json, or clears it when ReleaseNotesVersion doesn't match the tag, so old notes never ship - Keeps the MSIX artifact for 30 days instead of 90 Co-Authored-By: Claude Opus 5.5 <[email protected]>
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.
Summary
Releases can now go to the Microsoft Store automatically. A new
storejob inrelease.ymlruns after the existing release job and submits the MSIX bundle with the Microsoft Store CLI.It stays off until the repository variable
STORE_AUTO_PUBLISHistrue. The CLI can't make a first submission, and a submission still in certification blocks a new one, so turn it on once 4.2.0 is published.What the job does
msix-<version>artifact the release job built.microsoft/[email protected], pinned to CLIv0.4.4.STORE_TENANT_ID,STORE_CLIENT_ID,STORE_CLIENT_SECRETandSTORE_SELLER_IDsecrets, passed as environment variables.msstore publish <bundle> --appId 9P8H93Z0TGK4 --noCommit --uploadTimeout 3600makes a draft from the last published submission (listings, screenshots, pricing and markets carry over) and swaps in the new bundle. The timeout is raised because the bundle is about 122 MB and the default is 100 seconds.packaging/msix/store/set-release-notes.ps1sets "What's new" in every language fromlistings.json.msstore submission publishsends it to certification.Release notes guard
listings.jsongetscommon.ReleaseNotesVersion(now4.3.0). When it doesn't match the tag, the script clears "What's new" and the job shows a warning, so the previous release's notes never ship under a new version.The script edits the submission JSON with
System.Text.Json.Nodes, so dates and other fields go back untouched, and passes it tomsstore submission updateas a file, because the full submission is longer than a command line allows.Other changes
packaging/msix/store/README.mddescribe the job, the variable and the release steps.Testing
set-release-notes.ps1against sample submissions (-SubmissionFile): PascalCase and camelCase JSON, matching and stale versions. Notes are set or cleared as expected, other languages and fields are left alone, and a date string comes back unchanged.STORE_AUTO_PUBLISHis set.Reviewer notes
v0.4.4: publish takes the bundle as a file path with--appId;submission updateaccepts a JSON file path.v4.3.0is already tagged and released without this job.🤖 Generated with Claude Code