Skip to content

ci: 🚀 publish releases to the Microsoft Store - #43

Merged
amd989 merged 1 commit into
masterfrom
ci/store-publish
Nov 17, 2026
Merged

amd989 merged 1 commit into
masterfrom
ci/store-publish

Conversation

@amd989

@amd989 amd989 commented Nov 7, 2026

Copy link
Copy Markdown
Owner

Summary

Releases can now go to the Microsoft Store automatically. A new store job in release.yml runs after the existing release job and submits the MSIX bundle with the Microsoft Store CLI.

It stays off until the repository variable STORE_AUTO_PUBLISH is true. 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

  1. Downloads the msix-<version> artifact the release job built.
  2. Sets up the CLI with microsoft/[email protected], pinned to CLI v0.4.4.
  3. Signs in with the STORE_TENANT_ID, STORE_CLIENT_ID, STORE_CLIENT_SECRET and STORE_SELLER_ID secrets, passed as environment variables.
  4. msstore publish <bundle> --appId 9P8H93Z0TGK4 --noCommit --uploadTimeout 3600 makes 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.
  5. packaging/msix/store/set-release-notes.ps1 sets "What's new" in every language from listings.json.
  6. msstore submission publish sends it to certification.

Release notes guard

listings.json gets common.ReleaseNotesVersion (now 4.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 to msstore submission update as a file, because the full submission is longer than a command line allows.

Other changes

  • The MSIX artifact is kept for 30 days instead of 90. The store job uses it right away, and it is much bigger than the other artifacts.
  • CLAUDE.md and packaging/msix/store/README.md describe the job, the variable and the release steps.

Testing

  • set-release-notes.ps1 against 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.
  • The workflow's PowerShell blocks and the script parse cleanly; the new job's keys line up.
  • Not run: the job itself against Partner Center (needs the secrets and a published first submission), and actionlint (not available in this environment). The first real run will be the next tag after STORE_AUTO_PUBLISH is set.

Reviewer notes

  • CLI option names come from the msstore-cli source at v0.4.4: publish takes the bundle as a file path with --appId; submission update accepts a JSON file path.
  • Only "What's new" is synced. The description and features carry over from the last submission, so the reworded admin paragraph from feat: 📦 add Microsoft Store (MSIX) package #37 still needs one manual CSV import.
  • v4.3.0 is already tagged and released without this job.

🤖 Generated with Claude Code

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]>
@amd989
amd989 merged commit e1e8c73 into master Nov 17, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant