Document automatic update options for MSIX packages distributed through GitHub
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github
- Domain
- documentation, release
Research direction
Review the existing App Installer file schema, update settings, signing, and Microsoft Store distribution documentation referenced by the request. Confirm how stable HTTPS locations, package identity, publisher, and versioning affect GitHub-hosted packages. Done means the guidance explains supported automatic-update options and clearly states that a standalone MSIX release does not update automatically.
Written by the indexing model from the issue text.
Description
Documentation request
Provide guidance for developers who distribute MSIX packages through GitHub and want their applications to update automatically.
Proposed guidance
Recommend one of the following supported approaches:
- Publish an App Installer file (
.appinstaller) that references the MSIX package and configures automatic update behavior. Explain how this works when package releases are hosted on GitHub, including the need for stable HTTPS download locations and consistent package identity, publisher, signing, and versioning. - Publish a Microsoft Store-signed MSIX package through the Microsoft Store so the Store manages package updates.
Clarify that publishing a standalone MSIX package in a GitHub release does not, by itself, configure automatic updates. Include links to the existing App Installer file schema, update settings, signing, and Microsoft Store distribution documentation.
Intended outcome
Developers using GitHub can choose an appropriate distribution and update mechanism instead of expecting a directly downloaded MSIX package to discover and install updates automatically.
- Dominant language
- No language data
- Stars
- 82
- Forks
- 121
- Avg merge
- 16m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MicrosoftDocs/msix-docs
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
MicrosoftDocs/msix-docs#453 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
MicrosoftDocs/msix-docs#414 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
MicrosoftDocs/msix-docs#512 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
MicrosoftDocs/msix-docs#498 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 66/100
MicrosoftDocs/msix-docs#497 · 1 comment ·
All issues in MicrosoftDocs/msix-docs
Similar issues
-
user-reported
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Kong/developer.konghq.com#7316 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
bug triage:deciding
Difficulty 1/5 Under an hour Newbie friendliness 88/100
open-telemetry/otel-arrow#4132 ·
-
Ecosystem: ClawMetry — the Qwen Code reader is now free and open source (follow-up to #9294 / #9338) Opencategory/integration priority/P3 scope/documentation status/ready-for-human type/feature-request
Difficulty 1/5 Under an hour Newbie friendliness 84/100