Publish extension updates #5698

chatasweetie · 2025-10-14T20:22:32Z

I've fleshed out the guide of publishing to Store & WinGet for the first submission. It is still missing the automation of updates (not NEEDED but would be nice).

TODO for this PR:

Someone to review these steps to validate

… actions

…to being bold

prmerger-automator · 2025-10-14T20:22:42Z

@chatasweetie : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

learn-build-service-prod · 2025-10-14T20:24:43Z

Learn Build status updates of commit 79e4a30:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
hub/powertoys/command-palette/publish-extension.md	⚠️Warning		Details

hub/powertoys/command-palette/publish-extension.md

Line 45, Column 3: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/windows/apps/publish/partner-center/partner-center-developer-account' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 46, Column 68: [Warning: hard-coded-locale - See documentation] Link 'https://learn.microsoft.com/en-us/windows/apps/design/style/iconography/visual-studio-asset-generation' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 37, Column 250: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/windows/apps/publish/' will be broken in isolated environments. Replace with a relative link.
Line 45, Column 3: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/windows/apps/publish/partner-center/partner-center-developer-account' will be broken in isolated environments. Replace with a relative link.
Line 46, Column 68: [Suggestion: docs-link-absolute - See documentation] Absolute link 'https://learn.microsoft.com/en-us/windows/apps/design/style/iconography/visual-studio-asset-generation' will be broken in isolated environments. Replace with a relative link.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

alvinashcraft

Some fixes to address the build warnings. I'll take a closer look at the contents of the tutorial tomorrow. Thanks for updating this!

hub/powertoys/command-palette/publish-extension.md

chatasweetie · 2025-10-14T21:53:08Z

Thanks @alvinashcraft Before you do, Zach is going to walk through it to make sure it's not missing anything

hub/powertoys/command-palette/publish-extension.md

zateutsch

Microsoft store comments

hub/powertoys/command-palette/publish-extension.md

…card and point microsoft store expected naming, updated $projectFile file path to be one repo lower due to single extension different structure than my multi extension

learn-build-service-prod · 2025-10-27T16:35:35Z

Learn Build status updates of commit a3a9da7:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
hub/powertoys/command-palette/publish-extension.md	⚠️Warning		Details
uwp/index.yml	⚠️Warning		Details

hub/powertoys/command-palette/publish-extension.md

Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

uwp/index.yml

Line 12, Column 18: [Warning: ms-service-subservice-invalid - See documentation] Invalid value for 'ms.subservice': 'uwp-conceptual-docs' is not valid with 'ms.service' value 'uwp'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

hub/powertoys/command-palette/publish-extension.md

chatasweetie · 2025-10-30T20:52:25Z

@zadjii-msft
Here is the draft of publishing extensions

learn-build-service-prod · 2025-10-31T21:42:36Z

Learn Build status updates of commit c2b1618:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
hub/powertoys/command-palette/publish-extension.md	⚠️Warning		Details

hub/powertoys/command-palette/publish-extension.md

Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

* WinAppSDK 1.8 Preview 1 - Release Notes WinAppSDK 1.8 Preview 1 - Release Notes * Update preview-channel.md * Update preview-channel-1.7.md * Update preview-channel-1.7.md * rename * Updates * Update preview-channel.md * Update release-channels.md * Update downloads.md --------- Co-authored-by: KB <[email protected]>

… thanks Gleb!

learn-build-service-prod · 2025-11-03T22:50:58Z

Learn Build status updates of commit d9d9ce2:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
hub/powertoys/command-palette/publish-extension.md	⚠️Warning		Details

hub/powertoys/command-palette/publish-extension.md

Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

…ile, thanks Felipe!

learn-build-service-prod · 2025-11-03T23:31:13Z

Learn Build status updates of commit 4411cc7:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
hub/powertoys/command-palette/publish-extension.md	⚠️Warning		Details

hub/powertoys/command-palette/publish-extension.md

Line 45, Column 3: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/publish/partner-center/partner-center-developer-account'.
Line 46, Column 68: [Warning: file-not-found - See documentation] Invalid file link: '../../apps/design/style/iconography/visual-studio-asset-generation'.

For more details, please refer to the build report.

Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.

alvinashcraft

I ran the changes through the Learn Authoring Assistant. These are the style guide suggestions it gave.

alvinashcraft · 2025-11-04T14:34:36Z

hub/powertoys/command-palette/publish-extension.md

+# Publish Command Palette extensions

-The Command Palette provides a full extension model, allowing developers to create their own experiences for the palette. This document provides information about how to publish an extension.
+This article provides instructions for Command Palette extensions that were created using the Command Palette template.


Suggested change

This article provides instructions for Command Palette extensions that were created using the Command Palette template.

This article provides instructions for Command Palette extensions that you create with the Command Palette template.

alvinashcraft · 2025-11-04T14:35:08Z

hub/powertoys/command-palette/publish-extension.md

-## Pre-requisites
+## Microsoft Store
+
+Command Palette extensions can be published to the Microsoft Store. The publishing process is similar to other apps or extensions. You create a new submission in Partner Center and upload your `.msix` package. Command Palette automatically discovers your extension when users install it from the Microsoft Store.


Suggested change

Command Palette extensions can be published to the Microsoft Store. The publishing process is similar to other apps or extensions. You create a new submission in Partner Center and upload your `.msix` package. Command Palette automatically discovers your extension when users install it from the Microsoft Store.

You can publish Command Palette extensions to the Microsoft Store. The publishing process is similar to other apps or extensions. You create a new submission in Partner Center and upload your `.msix` package. Command Palette automatically discovers your extension when users install it from the Microsoft Store.

alvinashcraft · 2025-11-04T14:35:48Z

hub/powertoys/command-palette/publish-extension.md

+
+### Set up Microsoft Store
+
+1. Navigate to the [Microsoft Partner Center](https://partner.microsoft.com/dashboard/home).


Suggested change

1. Navigate to the [Microsoft Partner Center](https://partner.microsoft.com/dashboard/home).

1. Go to the [Microsoft Partner Center](https://partner.microsoft.com/dashboard/home).

alvinashcraft · 2025-11-04T14:36:05Z

hub/powertoys/command-palette/publish-extension.md

+1. Under **Workspaces**, select **Apps and games**.
+1. Select **+ New Product**.
+1. Select **MSIX or PWA app**.
+1. Create a name or reserve a product name.


Suggested change

1. Create a name or reserve a product name.

1. Create or reserve a product name.

alvinashcraft · 2025-11-04T14:37:01Z

hub/powertoys/command-palette/publish-extension.md

+> - **Package/Identity/Publisher**: `_________________`
+> - **Package/Properties/PublisherDisplayName**: `_________________`
+>
+> You'll use these exact values in the code examples below.


Suggested change

> You'll use these exact values in the code examples below.

> Use these exact values in the code examples.

alvinashcraft · 2025-11-04T14:56:48Z

hub/powertoys/command-palette/publish-extension.md

+
+1. Update the placeholders in `release-extension.yml`:
+1. git commit the 3 new files: `build-exe.ps1`, `setup.iss`,`release-extension.yml`
+1. Push changes to Github.


Suggested change

1. Push changes to Github.

1. Push changes to GitHub.

alvinashcraft · 2025-11-04T14:57:41Z

hub/powertoys/command-palette/publish-extension.md

+### WinGet submission
+
+> [!IMPORTANT]
+> The first submission must be manual. `wingetcreate new` requires interactive input for package details


Suggested change

> The first submission must be manual. `wingetcreate new` requires interactive input for package details

> You must manually submit the first version. `wingetcreate new` requires interactive input for package details.

alvinashcraft · 2025-11-04T14:58:16Z

hub/powertoys/command-palette/publish-extension.md

+   > [!TIP]
+   > To get the GitHub Release URL: Go to your release page, under **Assets**, right-click the `.exe` file and select "Copy link address".
+
+1. When `wingetcreate` prompts you, press **Enter** if the suggested response is pulled from the EXE file, for example: `PackageIdentifier`, `PackageVersion`, `Publisher`, etc.


Suggested change

1. When `wingetcreate` prompts you, press **Enter** if the suggested response is pulled from the EXE file, for example: `PackageIdentifier`, `PackageVersion`, `Publisher`, etc.

1. When `wingetcreate` prompts you, press **Enter** if the suggested response is pulled from the EXE file, for example: `PackageIdentifier`, `PackageVersion`, `Publisher`, and so on.

alvinashcraft · 2025-11-04T14:58:41Z

hub/powertoys/command-palette/publish-extension.md

+   - **Final submission question**:
+     - "Would you like to submit your manifest to the Windows Package Manager repository?" → **Yes**
+
+After answering "Yes" to submit:


Suggested change

After answering "Yes" to submit:

After you answer "Yes" to submit:

alvinashcraft · 2025-11-04T14:59:25Z

hub/powertoys/command-palette/publish-extension.md

+- Opens a pull request automatically
+- Provides the PR URL for tracking
+
+After submitting your pull request, the WinGet team will review your manifest for compliance and accuracy. You can monitor the PR status on GitHub and respond to any feedback from reviewers. Once approved and merged, your extension will be available through WinGet within a few hours.


Suggested change

After submitting your pull request, the WinGet team will review your manifest for compliance and accuracy. You can monitor the PR status on GitHub and respond to any feedback from reviewers. Once approved and merged, your extension will be available through WinGet within a few hours.

After you submit your pull request, the WinGet team reviews your manifest for compliance and accuracy. You can monitor the PR status on GitHub and respond to any feedback from reviewers. Once approved and merged, your extension is available through WinGet within a few hours.

alvinashcraft

I ran the changes through the Learn Authoring Assistant. These are the style guide suggestions it gave.

niels9001 · 2025-11-04T16:42:13Z

hub/powertoys/command-palette/publish-extension.md

+### Prepare the extension
+
+1. In your IDE, open `<ExtensionName>\Package.appxmanifest`.
+1. Replace the values with the information you copied from Partner Center:


Is this what Visual Studio does when right-clicking on your project and clicking "Associcate with Store"?

If so, I'd push this flow as it's much easier to go through vs manually copying stuff?

niels9001 · 2025-11-04T16:42:44Z

hub/powertoys/command-palette/publish-extension.md

+> **MSIX packages explained**
+> MSIX is Microsoft's modern app packaging format that provides secure installation, automatic updates, and clean uninstallation. It replaces older formats like MSI and ensures your extension integrates properly with Windows security and deployment features.
+
+Command Palette can't search for or install extensions that are only listed in the store. You can find those extensions by running the following command:


Suggested change

Command Palette can't search for or install extensions that are only listed in the store. You can find those extensions by running the following command:

Command Palette can't search for or install extensions that are only listed in the Store. You can find those extensions by running the following command:

niels9001 · 2025-11-04T16:42:59Z

hub/powertoys/command-palette/publish-extension.md

+
+> [!NOTE]
+> **MSIX packages explained**
+> MSIX is Microsoft's modern app packaging format that provides secure installation, automatic updates, and clean uninstallation. It replaces older formats like MSI and ensures your extension integrates properly with Windows security and deployment features.


Link to MSIX docs-hub?

niels9001 · 2025-11-04T16:44:41Z

hub/powertoys/command-palette/publish-extension.md

+## Guide to WinGet publishing

-<!-- 
+Publishing to WinGet is the recommended distribution method for Command Palette extensions as it enables automatic discovery and installation directly within Command Palette. This guide covers the majority of the WinGet publication process, from preparing your project and creating build scripts to setting up GitHub Actions automation and submitting your first package manifest. You'll learn how to create installer packages, configure automated builds, and navigate the WinGet submission workflow to make your extension easily discoverable and installable for users.


Is it the recommended distribution method (long term)? @zadjii-msft ?

jiripolasek · 2025-11-04T20:00:21Z

hub/powertoys/command-palette/publish-extension.md

+1. Locate the MSIX files:
+
+   ```powershell
+   dir AppPackages -Recurse -Filter "*.msix"


[nit] some PWSH fragments use ls, some dir

jiripolasek · 2025-11-05T10:05:20Z

hub/powertoys/command-palette/publish-extension.md

+
+```xml
+<Identity
+    Name="YOUR_PACKAGE_IDENTITY_NAME_HERE" <!-- Replace with your Package/Identity/Name -->


This is invalid HTML syntax (HTML comment inside an HTML tag), which could disrupt syntax highlighting. I'm not sure if it affects MS Learn, but it definitely causes issues in GitHub.

chatasweetie added 4 commits October 14, 2025 10:20

microsoft store and winget instructions publishing content

68ed78c

update scripts

9ef2a58

correct formatting, add context to the two processes and about github…

e0823ca

… actions

minor formatting changes, moved two requirements for winget from ### …

79e4a30

…to being bold

prmerger-automator bot added the do-not-merge label Oct 14, 2025

prmerger-automator bot assigned alvinashcraft Oct 14, 2025

prmerger-automator bot requested a review from alvinashcraft October 14, 2025 20:22

prmerger-automator bot added Change sent to author dev-environment/svc powertoys/subsvc labels Oct 14, 2025

alvinashcraft reviewed Oct 14, 2025

View reviewed changes

hub/powertoys/command-palette/publish-extension.md Outdated Show resolved Hide resolved

hub/powertoys/command-palette/publish-extension.md Outdated Show resolved Hide resolved

hub/powertoys/command-palette/publish-extension.md Outdated Show resolved Hide resolved

chatasweetie commented Oct 17, 2025

View reviewed changes

hub/powertoys/command-palette/publish-extension.md Outdated Show resolved Hide resolved

zateutsch reviewed Oct 17, 2025

View reviewed changes

add more microsoft store image and Partner Center details

1e991d2

zateutsch reviewed Oct 23, 2025

View reviewed changes

hub/powertoys/command-palette/publish-extension.md Outdated Show resolved Hide resolved

hub/powertoys/command-palette/publish-extension.md Outdated Show resolved Hide resolved

hub/powertoys/command-palette/publish-extension.md Outdated Show resolved Hide resolved

chatasweetie added 2 commits October 24, 2025 15:24

added more details about required images, made image upload as a wile…

b7d7705

…card and point microsoft store expected naming, updated $projectFile file path to be one repo lower due to single extension different structure than my multi extension

made changes based on Zachary's review

a3a9da7

chatasweetie commented Oct 30, 2025

View reviewed changes

hub/powertoys/command-palette/publish-extension.md Show resolved Hide resolved

update installer creation to include ARM64, add update github action

c2b1618

for gh actions added global variables to make script updating easier,…

d9d9ce2

… thanks Gleb!

updated gh actions and ps1 files to use variables at the top of the f…

4411cc7

…ile, thanks Felipe!

jiripolasek mentioned this pull request Nov 4, 2025

CmdPal: Make new extension template instantly publishable to Store microsoft/PowerToys#43240

Open

alvinashcraft reviewed Nov 4, 2025

View reviewed changes

niels9001 reviewed Nov 4, 2025

View reviewed changes

jiripolasek reviewed Nov 4, 2025

View reviewed changes

jiripolasek reviewed Nov 5, 2025

View reviewed changes

	This article provides instructions for Command Palette extensions that were created using the Command Palette template.
	This article provides instructions for Command Palette extensions that you create with the Command Palette template.

	Command Palette extensions can be published to the Microsoft Store. The publishing process is similar to other apps or extensions. You create a new submission in Partner Center and upload your `.msix` package. Command Palette automatically discovers your extension when users install it from the Microsoft Store.
	You can publish Command Palette extensions to the Microsoft Store. The publishing process is similar to other apps or extensions. You create a new submission in Partner Center and upload your `.msix` package. Command Palette automatically discovers your extension when users install it from the Microsoft Store.


		### Set up Microsoft Store

		1. Navigate to the [Microsoft Partner Center](https://partner.microsoft.com/dashboard/home).

	1. Navigate to the [Microsoft Partner Center](https://partner.microsoft.com/dashboard/home).
	1. Go to the [Microsoft Partner Center](https://partner.microsoft.com/dashboard/home).

	1. Create a name or reserve a product name.
	1. Create or reserve a product name.

	> You'll use these exact values in the code examples below.
	> Use these exact values in the code examples.

	> The first submission must be manual. `wingetcreate new` requires interactive input for package details
	> You must manually submit the first version. `wingetcreate new` requires interactive input for package details.

	1. When `wingetcreate` prompts you, press Enter if the suggested response is pulled from the EXE file, for example: `PackageIdentifier`, `PackageVersion`, `Publisher`, etc.
	1. When `wingetcreate` prompts you, press Enter if the suggested response is pulled from the EXE file, for example: `PackageIdentifier`, `PackageVersion`, `Publisher`, and so on.

	After answering "Yes" to submit:
	After you answer "Yes" to submit:

	After submitting your pull request, the WinGet team will review your manifest for compliance and accuracy. You can monitor the PR status on GitHub and respond to any feedback from reviewers. Once approved and merged, your extension will be available through WinGet within a few hours.
	After you submit your pull request, the WinGet team reviews your manifest for compliance and accuracy. You can monitor the PR status on GitHub and respond to any feedback from reviewers. Once approved and merged, your extension is available through WinGet within a few hours.

	Command Palette can't search for or install extensions that are only listed in the store. You can find those extensions by running the following command:
	Command Palette can't search for or install extensions that are only listed in the Store. You can find those extensions by running the following command:

Publish extension updates #5698

Are you sure you want to change the base?

Publish extension updates #5698

Conversation

chatasweetie commented Oct 14, 2025

Uh oh!

prmerger-automator bot commented Oct 14, 2025

Uh oh!

learn-build-service-prod bot commented Oct 14, 2025

⚠️ Validation status: warnings

Uh oh!

alvinashcraft left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

chatasweetie commented Oct 14, 2025

Uh oh!

Uh oh!

zateutsch left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

learn-build-service-prod bot commented Oct 27, 2025

⚠️ Validation status: warnings

Uh oh!

Uh oh!

chatasweetie commented Oct 30, 2025

Uh oh!

learn-build-service-prod bot commented Oct 31, 2025

⚠️ Validation status: warnings

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

⚠️ Validation status: warnings

Uh oh!

learn-build-service-prod bot commented Nov 3, 2025

⚠️ Validation status: warnings

Uh oh!

alvinashcraft left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

alvinashcraft left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment