Document that an app can't move from .msixbundle back to a standalone .msix - #508
Draft
Roy (RDMacLachlan) wants to merge 3 commits into
Draft
Document that an app can't move from .msixbundle back to a standalone .msix#508Roy (RDMacLachlan) wants to merge 3 commits into
Roy (RDMacLachlan) wants to merge 3 commits into
Conversation
… .msix Document the package-type update constraint for ADO bug 31767253. A package family can move from a standalone .msix package to an .msixbundle, but later updates cannot move from the bundle back to a standalone .msix package. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 4b5b11f6-6bf8-4401-90b8-68f710728c8e
Removed SME question comment regarding update constraints.
Contributor
|
Learn Build status updates of commit 64f52c2: ✅ Validation status: passed
For more details, please refer to the build report. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates MSIX documentation to clarify update constraints when transitioning between standalone .msix packages and .msixbundle bundles for the same package family, ensuring authors and publishers don’t plan unsupported “bundle → standalone” update paths.
Changes:
- Clarifies in the bundling overview that once a package family ships as an
.msixbundle, subsequent updates can’t revert to a standalone.msix. - Expands the “App update constraints” guidance to explicitly document the one-way transition:
.msix→.msixbundleis supported, but not the reverse. - Refreshes
ms.datemetadata for both affected articles.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| msix-src/package/bundling-overview.md | Adds a dedicated section documenting the one-way update constraint and links to the detailed updates article. |
| msix-src/app-package-updates.md | Splits the previous single note into clearer, explicit subsections covering allowed and disallowed transitions. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Learn Build status updates of commit bbaf63e: ✅ Validation status: passed
For more details, please refer to the build report. |
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
Documents that a package family can move from a standalone .msix package to an .msixbundle, but subsequent updates cannot move from the bundle back to a standalone .msix package.
Related work item
Resolves AB#31767253.
ADO bug: https://dev.azure.com/microsoft/OS/_workitems/edit/31767253