From 40123de8d80974ff9982d187d6756ceaf319773f Mon Sep 17 00:00:00 2001 From: Yidi Mao Date: Fri, 16 Oct 2026 03:57:43 +0300 Subject: [PATCH 1/2] ci: add opt-in Microsoft Store publish job and msstore-cli skill Document the published Store listing and winget msstore install path. --- .claude/skills/msstore-cli/SKILL.md | 600 ++++++++++++++++++++++++++++ .github/workflows/release-msix.yml | 57 +++ CLAUDE.md | 5 +- docs/PUBLISHING.md | 17 + skills-lock.json | 6 + 5 files changed, 683 insertions(+), 2 deletions(-) create mode 100644 .claude/skills/msstore-cli/SKILL.md diff --git a/.claude/skills/msstore-cli/SKILL.md b/.claude/skills/msstore-cli/SKILL.md new file mode 100644 index 0000000..4cd4338 --- /dev/null +++ b/.claude/skills/msstore-cli/SKILL.md @@ -0,0 +1,600 @@ +--- +name: msstore-cli +description: 'Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.' +license: MIT +--- + +# Microsoft Store Developer CLI (msstore) + +The Microsoft Store Developer CLI (`msstore`) is a cross-platform command-line interface for publishing and managing applications in the Microsoft Store. It integrates with Partner Center APIs and supports automated publishing workflows for various application types. + +## When to Use This Skill + +Use this skill when you need to: + +- Configure Store credentials for API access +- List applications in your Store account +- Check the status of a submission +- Publish submissions to the Store +- Package applications for Store submission +- Initialize projects for Store publishing +- Manage package flights (beta testing) +- Set up CI/CD pipelines for automated Store publishing +- Manage gradual rollouts of submissions +- Update submission metadata programmatically + +## Prerequisites + +- Windows 10+, macOS, or Linux +- .NET 9 Desktop Runtime (Windows) or .NET 9 Runtime (macOS/Linux) +- Partner Center account with appropriate permissions +- Azure AD app registration with Partner Center API access +- msstore CLI installed via one of these methods: + - **Microsoft Store**: [Download](https://www.microsoft.com/store/apps/9P53PC5S0PHJ) + - **WinGet**: `winget install "Microsoft Store Developer CLI"` + - **Manual**: Download from [GitHub Releases](https://aka.ms/msstoredevcli/releases) + +### Partner Center Setup + +Before using msstore, you need to create an Azure AD application with Partner Center access: + +1. Go to [Partner Center](https://partner.microsoft.com/dashboard) +2. Navigate to **Account settings** > **User management** > **Azure AD applications** +3. Create a new application and note the **Tenant ID**, **Client ID**, and **Client Secret** +4. Grant the application appropriate permissions (Manager or Developer role) + +## Core Commands Reference + +### info - Print Configuration + +Display the current credential configuration. + +```bash +msstore info +``` + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `-v, --verbose` | Print verbose output | + +### reconfigure - Configure Credentials + +Configure or update Microsoft Store API credentials. + +```bash +msstore reconfigure [options] +``` + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `-t, --tenantId` | Azure AD Tenant ID | +| `-s, --sellerId` | Partner Center Seller ID | +| `-c, --clientId` | Azure AD Application Client ID | +| `-cs, --clientSecret` | Client Secret for authentication | +| `-ct, --certificateThumbprint` | Certificate thumbprint (alternative to client secret) | +| `-cfp, --certificateFilePath` | Certificate file path (alternative to client secret) | +| `-cp, --certificatePassword` | Certificate password | +| `--reset` | Reset credentials without full reconfiguration | + +**Examples:** + +```bash +# Configure with client secret +msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --clientSecret $CLIENT_SECRET + +# Configure with certificate +msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --certificateFilePath ./cert.pfx --certificatePassword MyPassword +``` + +### settings - CLI Settings + +Change settings of the Microsoft Store Developer CLI. + +```bash +msstore settings [options] +``` + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `-t, --enableTelemetry` | Enable (true) or disable (false) telemetry | + +#### Set Publisher Display Name + +```bash +msstore settings setpdn +``` + +Sets the default Publisher Display Name for the `init` command. + +### apps - Application Management + +List and retrieve application information. + +#### List Applications + +```bash +msstore apps list +``` + +Lists all applications in your Partner Center account. + +#### Get Application Details + +```bash +msstore apps get +``` + +**Arguments:** + +| Argument | Description | +| -------- | ----------- | +| `productId` | The Store product ID (e.g., 9NBLGGH4R315) | + +**Example:** + +```bash +# Get details of a specific app +msstore apps get 9NBLGGH4R315 +``` + +### submission - Submission Management + +Manage Store submissions. + +| Sub-Command | Description | +| ----------- | ----------- | +| `status` | Get submission status | +| `get` | Get submission metadata and package info | +| `getListingAssets` | Get listing assets of a submission | +| `updateMetadata` | Update submission metadata | +| `poll` | Poll submission status until complete | +| `publish` | Publish a submission | +| `delete` | Delete a submission | + +#### Get Submission Status + +```bash +msstore submission status +``` + +#### Get Submission Details + +```bash +msstore submission get +``` + +#### Update Metadata + +```bash +msstore submission updateMetadata +``` + +Where `` is a JSON string with the updated metadata. Because JSON contains characters that shells interpret (quotes, braces, etc.), you must quote and/or escape the value appropriately: + +- **Bash/Zsh**: Wrap the JSON in single quotes so the shell passes it through literally. + ```bash + msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}' + ``` +- **PowerShell**: Use single quotes (or escape double quotes inside a double-quoted string). + ```powershell + msstore submission updateMetadata 9NBLGGH4R315 '{"description":"My updated app"}' + ``` +- **cmd.exe**: Escape each inner double quote with a backslash. + ```cmd + msstore submission updateMetadata 9NBLGGH4R315 "{\"description\":\"My updated app\"}" + ``` + +> **Tip:** For complex or multi-line metadata, save the JSON to a file and pass its contents instead to avoid quoting issues: +> ```bash +> msstore submission updateMetadata 9NBLGGH4R315 "$(cat metadata.json)" +> ``` + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `-s, --skipInitialPolling` | Skip initial status polling | + +#### Publish Submission + +```bash +msstore submission publish +``` + +#### Poll Submission + +```bash +msstore submission poll +``` + +Polls until the submission status is PUBLISHED or FAILED. + +#### Delete Submission + +```bash +msstore submission delete +``` + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `--no-confirm` | Skip confirmation prompt | + +### init - Initialize Project for Store + +Initialize a project for Microsoft Store publishing. Automatically detects project type and configures Store identity. + +```bash +msstore init [options] +``` + +**Arguments:** + +| Argument | Description | +| -------- | ----------- | +| `pathOrUrl` | Project directory path or PWA URL | + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `-n, --publisherDisplayName` | Publisher Display Name | +| `--package` | Also package the project | +| `--publish` | Package and publish (implies --package) | +| `-f, --flightId` | Publish to a specific flight | +| `-prp, --packageRolloutPercentage` | Gradual rollout percentage (0-100) | +| `-a, --arch` | Architecture(s): x86, x64, arm64 | +| `-o, --output` | Output directory for packages | +| `-ver, --version` | Version to use when building | + +**Supported Project Types:** + +- Windows App SDK / WinUI 3 +- UWP +- .NET MAUI +- Flutter +- Electron +- React Native for Desktop +- PWA (Progressive Web Apps) + +**Examples:** + +```bash +# Initialize WinUI project +msstore init ./my-winui-app + +# Initialize PWA +msstore init https://contoso.com --output ./pwa-package + +# Initialize and publish +msstore init ./my-app --publish +``` + +### package - Package for Store + +Package an application for Microsoft Store submission. + +```bash +msstore package [options] +``` + +**Arguments:** + +| Argument | Description | +| -------- | ----------- | +| `pathOrUrl` | Project directory path or PWA URL | + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `-o, --output` | Output directory for the package | +| `-a, --arch` | Architecture(s): x86, x64, arm64 | +| `-ver, --version` | Version for the package | + +**Examples:** + +```bash +# Package for default architecture +msstore package ./my-app + +# Package for multiple architectures +msstore package ./my-app --arch x64,arm64 --output ./packages + +# Package with specific version +msstore package ./my-app --version 1.2.3.0 +``` + +### publish - Publish to Store + +Publish an application to the Microsoft Store. + +```bash +msstore publish [options] +``` + +**Arguments:** + +| Argument | Description | +| -------- | ----------- | +| `pathOrUrl` | Project directory path or PWA URL | + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `-i, --inputFile` | Path to existing .msix or .msixupload file | +| `-id, --appId` | Application ID (if not initialized) | +| `-nc, --noCommit` | Keep submission in draft state | +| `-f, --flightId` | Publish to a specific flight | +| `-prp, --packageRolloutPercentage` | Gradual rollout percentage (0-100) | + +**Examples:** + +```bash +# Publish project +msstore publish ./my-app + +# Publish existing package +msstore publish ./my-app --inputFile ./packages/MyApp.msixupload + +# Publish as draft +msstore publish ./my-app --noCommit + +# Publish with gradual rollout +msstore publish ./my-app --packageRolloutPercentage 10 +``` + +### flights - Package Flight Management + +Manage package flights (beta testing groups). + +| Sub-Command | Description | +| ----------- | ----------- | +| `list` | List all flights for an app | +| `get` | Get flight details | +| `delete` | Delete a flight | +| `create` | Create a new flight | +| `submission` | Manage flight submissions | + +#### List Flights + +```bash +msstore flights list +``` + +#### Get Flight Details + +```bash +msstore flights get +``` + +#### Create Flight + +```bash +msstore flights create --group-ids +``` + +**Options:** + +| Option | Description | +| ------ | ----------- | +| `-g, --group-ids` | Flight group IDs (comma-separated) | +| `-r, --rank-higher-than` | Flight ID to rank higher than | + +#### Delete Flight + +```bash +msstore flights delete +``` + +#### Flight Submissions + +```bash +# Get flight submission +msstore flights submission get + +# Publish flight submission +msstore flights submission publish + +# Check flight submission status +msstore flights submission status + +# Poll flight submission +msstore flights submission poll + +# Delete flight submission +msstore flights submission delete +``` + +#### Flight Rollout Management + +```bash +# Get rollout status +msstore flights submission rollout get + +# Update rollout percentage +msstore flights submission rollout update + +# Halt rollout +msstore flights submission rollout halt + +# Finalize rollout (100%) +msstore flights submission rollout finalize +``` + +## Common Workflows + +### Workflow 1: First-Time Store Setup + +```bash +# 1. Install the CLI +winget install "Microsoft Store Developer CLI" + +# 2. Configure credentials (get these from Partner Center) +msstore reconfigure --tenantId $TENANT_ID --sellerId $SELLER_ID --clientId $CLIENT_ID --clientSecret $CLIENT_SECRET + +# 3. Verify configuration +msstore info + +# 4. List your apps to confirm access +msstore apps list +``` + +### Workflow 2: Initialize and Publish New App + +```bash +# 1. Navigate to project +cd my-winui-app + +# 2. Initialize for Store (creates/updates app identity) +msstore init . + +# 3. Package the application +msstore package . --arch x64,arm64 + +# 4. Publish to Store +msstore publish . + +# 5. Check submission status +msstore submission status +``` + +### Workflow 3: Update Existing App + +```bash +# 1. Build your updated application +dotnet publish -c Release + +# 2. Package and publish +msstore publish ./my-app + +# Or publish from existing package +msstore publish ./my-app --inputFile ./artifacts/MyApp.msixupload +``` + +### Workflow 4: Gradual Rollout + +```bash +# 1. Publish with initial rollout percentage +msstore publish ./my-app --packageRolloutPercentage 10 + +# 2. Monitor and increase rollout +msstore submission poll + +# 3. (After validation) Finalize to 100% +# This completes via Partner Center or submission update +``` + +### Workflow 5: Beta Testing with Flights + +```bash +# 1. Create a flight group in Partner Center first +# Then create a flight +msstore flights create "Beta Testers" --group-ids "group-id-1,group-id-2" + +# 2. Publish to the flight +msstore publish ./my-app --flightId + +# 3. Check flight submission status +msstore flights submission status + +# 4. After testing, publish to production +msstore publish ./my-app +``` + +### Workflow 6: CI/CD Pipeline Integration + +```yaml +# GitHub Actions example +name: Publish to Store + +on: + release: + types: [published] + +jobs: + publish: + runs-on: windows-latest + steps: + - uses: actions/checkout@v4 + + - name: Setup .NET + uses: actions/setup-dotnet@v4 + with: + dotnet-version: '9.0.x' + + - name: Install msstore CLI + run: winget install "Microsoft Store Developer CLI" --accept-package-agreements --accept-source-agreements + + - name: Configure Store credentials + run: | + msstore reconfigure --tenantId ${{ secrets.TENANT_ID }} --sellerId ${{ secrets.SELLER_ID }} --clientId ${{ secrets.CLIENT_ID }} --clientSecret ${{ secrets.CLIENT_SECRET }} + + - name: Build application + run: dotnet publish -c Release + + - name: Publish to Store + run: msstore publish ./src/MyApp +``` + +## Integration with winapp CLI + +The winapp CLI (v0.2.0+) integrates with msstore via the `winapp store` subcommand: + +```bash +# These commands are equivalent: +msstore reconfigure --tenantId xxx --clientId xxx --clientSecret xxx +winapp store reconfigure --tenantId xxx --clientId xxx --clientSecret xxx + +# List apps +msstore apps list +winapp store apps list + +# Publish +msstore publish ./my-app +winapp store publish ./my-app +``` + +Use `winapp store` when you want a unified CLI experience for both packaging and publishing. + +## Troubleshooting + +| Issue | Solution | +| ----- | -------- | +| Authentication failed | Verify credentials with `msstore info`; re-run `msstore reconfigure` | +| App not found | Ensure the product ID is correct; run `msstore apps list` to verify | +| Insufficient permissions | Check Azure AD app role in Partner Center (needs Manager or Developer) | +| Package validation failed | Ensure package meets Store requirements; check Partner Center for details | +| Submission stuck | Run `msstore submission poll ` to check status | +| Flight not found | Verify flight ID with `msstore flights list ` | +| Rollout percentage invalid | Value must be between 0 and 100 | +| Init fails for PWA | Ensure URL is publicly accessible and has valid web app manifest | + +## Environment Variables + +The CLI supports environment variables for credentials: + +| Variable | Description | +| -------- | ----------- | +| `MSSTORE_TENANT_ID` | Azure AD Tenant ID | +| `MSSTORE_SELLER_ID` | Partner Center Seller ID | +| `MSSTORE_CLIENT_ID` | Azure AD Application Client ID | +| `MSSTORE_CLIENT_SECRET` | Client Secret | + +## References + +- [Microsoft Store Developer CLI Documentation](https://learn.microsoft.com/windows/apps/publish/msstore-dev-cli/overview) +- [CLI Commands Reference](https://learn.microsoft.com/windows/apps/publish/msstore-dev-cli/commands) +- [GitHub Repository](https://github.com/microsoft/msstore-cli) +- [Partner Center API](https://learn.microsoft.com/windows/uwp/monetize/using-windows-store-services) +- [App Submission API](https://learn.microsoft.com/windows/uwp/monetize/create-and-manage-submissions-using-windows-store-services) +- [Package Flights Overview](https://learn.microsoft.com/windows/uwp/publish/package-flights) +- [Gradual Package Rollout](https://learn.microsoft.com/windows/uwp/publish/gradual-package-rollout) diff --git a/.github/workflows/release-msix.yml b/.github/workflows/release-msix.yml index 0f0f320..afb3a1e 100644 --- a/.github/workflows/release-msix.yml +++ b/.github/workflows/release-msix.yml @@ -214,3 +214,60 @@ jobs: } gh release upload $tag ${{ steps.bundle.outputs.path }} $env:CER_PATH --clobber + + store-publish: + # Opt-in: set repo variable STORE_PUBLISH=true after adding the Partner Center secrets. + # Put required reviewers on the "microsoft-store" environment to gate each submission. + if: vars.STORE_PUBLISH == 'true' + needs: build-sign-release + runs-on: windows-latest + timeout-minutes: 30 + environment: microsoft-store + + defaults: + run: + shell: pwsh + + env: + STORE_PRODUCT_ID: 9NVSJZ72LTZ3 + + steps: + - name: Download signed bundle + uses: actions/download-artifact@9000827ccba6bdab643e8b6fd33ac0654aef8333 # v8 + with: + name: signed-msix + path: bundle + + - name: Find MSIX bundle + id: bundle + run: | + $bundle = Get-ChildItem -Path bundle -Recurse -Filter *.msixbundle | Select-Object -First 1 + if (-not $bundle) { + throw 'No .msixbundle in the signed-msix artifact.' + } + "path=$($bundle.FullName)" | Out-File -FilePath $env:GITHUB_OUTPUT -Append -Encoding utf8 + + - name: Setup Microsoft Store CLI + uses: microsoft/microsoft-store-apppublisher@15abd1c50fcc164b19cb240fb04ef3c49bf715a2 # v1.1 + + - name: Configure Store credentials + env: + TENANT_ID: ${{ secrets.PARTNER_CENTER_TENANT_ID }} + SELLER_ID: ${{ secrets.PARTNER_CENTER_SELLER_ID }} + CLIENT_ID: ${{ secrets.PARTNER_CENTER_CLIENT_ID }} + CLIENT_SECRET: ${{ secrets.PARTNER_CENTER_CLIENT_SECRET }} + run: | + msstore reconfigure ` + --tenantId $env:TENANT_ID ` + --sellerId $env:SELLER_ID ` + --clientId $env:CLIENT_ID ` + --clientSecret $env:CLIENT_SECRET + if ($LASTEXITCODE -ne 0) { throw "msstore reconfigure failed ($LASTEXITCODE)" } + + - name: Publish to Microsoft Store + run: | + msstore publish '${{ steps.bundle.outputs.path }}' -id $env:STORE_PRODUCT_ID + if ($LASTEXITCODE -ne 0) { throw "msstore publish failed ($LASTEXITCODE)" } + + - name: Wait for certification + run: msstore submission poll $env:STORE_PRODUCT_ID diff --git a/CLAUDE.md b/CLAUDE.md index e5466af..4ab7172 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -7,6 +7,7 @@ AI agent instructions for this repo. Verified against the tree on 2026-10-16. Command Palette (PowerToys) extension that lists Unity Hub projects and opens them in the Unity Editor. Reads `%APPDATA%\UnityHub\projects-v1.json`. .NET 10 (`net10.0-windows10.0.26100.0`), MSIX-packaged, trimmed/AOT-compatible. Store identity: `YidiMao.CommandPalette-Unity` (private values in git-ignored `docs/store-identity.md`). +Published on the Microsoft Store as "Project Launcher for Unity", product ID `9NVSJZ72LTZ3` (https://apps.microsoft.com/detail/9nvsjz72ltz3). Also installable via `winget install 9NVSJZ72LTZ3 -s msstore`. Updates go through `msstore` / the opt-in `store-publish` job in `release-msix.yml` (see `docs/PUBLISHING.md`); first submission was via Partner Center. ## Layout @@ -25,10 +26,10 @@ Store identity: `YidiMao.CommandPalette-Unity` (private values in git-ignored `d - Microsoft Learn MCP `microsoft-learn` (`https://learn.microsoft.com/api/mcp`, shared via `.mcp.json`): `microsoft_docs_search`, `microsoft_docs_fetch`, `microsoft_code_sample_search` - Fallback CLI: `npx @microsoft/learn-cli search|fetch|code-search`; `doctor` checks connectivity - Own skills (`.claude/skills/`, editable, in scope for refactors): `deploy`, `release`, `bump-deps` -- Third-party skills (managed by `bunx skills`, tracked in `skills-lock.json`; never hand-edit or refactor): `microsoft-docs`, `microsoft-code-reference` (`MicrosoftDocs/mcp`); `publish-extension`, `add-extension-settings`, `add-dock-band` (official PowerToys extension template) +- Third-party skills (managed by `bunx skills`, tracked in `skills-lock.json`; never hand-edit or refactor): `microsoft-docs`, `microsoft-code-reference` (`MicrosoftDocs/mcp`); `msstore-cli` (`github/awesome-copilot`); `publish-extension`, `add-extension-settings`, `add-dock-band` (official PowerToys extension template) - Add: `bunx skills add -s -a claude-code --copy -y`; update: `bunx skills update -p -y`; list: `bunx skills list`; restore: `bunx skills experimental_install` - Rule `.claude/rules/cmdpal-extension.md` (vendored from the PowerToys extension template, path-scoped to `UnityExtension/**/*.cs`; never hand-edit): Command Palette API reference and common mistakes -- CLIs (winget): `winapp` (Microsoft.WinAppCli: `run`/`unregister` dev registration, `cert`, `package`, `sign`, `ui` inspects the live Command Palette window) `actionlint` (also a pre-commit hook for `.github/workflows/`), and `msstore` (Store submissions; needs Partner Center credentials via `msstore reconfigure`, not configured) +- CLIs (winget): `winapp` (Microsoft.WinAppCli: `run`/`unregister` dev registration, `cert`, `package`, `sign`, `ui` inspects the live Command Palette window) `actionlint` (also a pre-commit hook for `.github/workflows/`), and `msstore` (Store submissions; needs Partner Center credentials via `msstore reconfigure`, not configured locally; see skill `msstore-cli`) - Recent Learn docs cover newer SDK surface (e.g. Dock bands); check them before assuming an API is missing ## Code rules diff --git a/docs/PUBLISHING.md b/docs/PUBLISHING.md index fa55b4e..4eee7a1 100644 --- a/docs/PUBLISHING.md +++ b/docs/PUBLISHING.md @@ -110,6 +110,23 @@ For local-dev tester trust, keep one reusable signing cert and store the private - `MSIX_PFX_PASSWORD` — the PFX password - `UnityExtension\BundleArtifacts\Maoyeedy-MSIX-LocalDev.cer` — public certificate for testers +### Microsoft Store updates (automated) + +The first Store submission was done in Partner Center; updates can use the `store-publish` job in `release-msix.yml`. It is off until you opt in: + +1. Partner Center > Account settings > User management > Microsoft Entra applications: create an app and note tenant ID, client ID, and a client secret. Note the seller ID (Account settings > Organization profile > Legal info). +2. Repo secrets: `PARTNER_CENTER_TENANT_ID`, `PARTNER_CENTER_SELLER_ID`, `PARTNER_CENTER_CLIENT_ID`, `PARTNER_CENTER_CLIENT_SECRET`. +3. Repo variable `STORE_PUBLISH=true`. +4. Settings > Environments > `microsoft-store`: add yourself as required reviewer so each submission waits for approval. + +On a `v*` tag the job downloads the built bundle and runs `msstore publish -id 9NVSJZ72LTZ3`, then `msstore submission poll`. The Store re-signs the package, so the self-signed PFX does not matter. Only free apps are supported by the CLI; the version must be higher than the last published one. + +Local equivalent: `msstore reconfigure ...`, then `msstore publish -id 9NVSJZ72LTZ3 --noCommit` (draft), `msstore submission get 9NVSJZ72LTZ3`, `msstore submission publish 9NVSJZ72LTZ3`. Run `publish` before editing listing metadata, because it discards a pending draft. + +### WinGet + +The Store listing is already installable with `winget install 9NVSJZ72LTZ3 -s msstore`; no extra setup is needed. Submitting to `microsoft/winget-pkgs` (the `windows-commandpalette-extension` tag route in the `publish-extension` skill) needs a separate unpackaged EXE installer (Inno Setup, `WindowsPackageType=None`) and is not set up. + ## CmdPal gallery submission Gallery metadata lives in the `microsoft/CmdPal-Extensions` repo, not here: `extensions/maoyeedy/cmdpal-unity-extension/` (`extension.json`, `icon.png`, `screenshots/`). The install source is `msstore` with ID `9NVSJZ72LTZ3`. Update that repo when the title, description, icon or screenshots change. diff --git a/skills-lock.json b/skills-lock.json index 3544f93..463137b 100644 --- a/skills-lock.json +++ b/skills-lock.json @@ -27,6 +27,12 @@ "skillPath": "skills/microsoft-docs/SKILL.md", "computedHash": "0acd8d2629937e021d605fd1426e641295909e13bab47cad1153793f5564e85e" }, + "msstore-cli": { + "source": "github/awesome-copilot", + "sourceType": "github", + "skillPath": "skills/msstore-cli/SKILL.md", + "computedHash": "abaef9913fe8c0d039ed3a6966d513656882c538cc3088d9c709ad78c00c3c7e" + }, "publish-extension": { "source": "microsoft/PowerToys", "ref": "main", From bd8a5b662534b0353fa1734589126cee5c01c338 Mon Sep 17 00:00:00 2001 From: Yidi Mao Date: Fri, 16 Oct 2026 05:14:33 +0300 Subject: [PATCH 2/2] docs: document Store publish setup and gotchas --- docs/PUBLISHING.md | 25 ++++++++++++++++++------- 1 file changed, 18 insertions(+), 7 deletions(-) diff --git a/docs/PUBLISHING.md b/docs/PUBLISHING.md index 4eee7a1..81b88c9 100644 --- a/docs/PUBLISHING.md +++ b/docs/PUBLISHING.md @@ -112,16 +112,27 @@ For local-dev tester trust, keep one reusable signing cert and store the private ### Microsoft Store updates (automated) -The first Store submission was done in Partner Center; updates can use the `store-publish` job in `release-msix.yml`. It is off until you opt in: +The first Store submission was done in Partner Center; updates can use the `store-publish` job in `release-msix.yml`. It is off until you opt in. -1. Partner Center > Account settings > User management > Microsoft Entra applications: create an app and note tenant ID, client ID, and a client secret. Note the seller ID (Account settings > Organization profile > Legal info). -2. Repo secrets: `PARTNER_CENTER_TENANT_ID`, `PARTNER_CENTER_SELLER_ID`, `PARTNER_CENTER_CLIENT_ID`, `PARTNER_CENTER_CLIENT_SECRET`. -3. Repo variable `STORE_PUBLISH=true`. -4. Settings > Environments > `microsoft-store`: add yourself as required reviewer so each submission waits for approval. +One-time setup: -On a `v*` tag the job downloads the built bundle and runs `msstore publish -id 9NVSJZ72LTZ3`, then `msstore submission poll`. The Store re-signs the package, so the self-signed PFX does not matter. Only free apps are supported by the CLI; the version must be higher than the last published one. +1. Partner Center > Account settings > Tenants: create or associate a Microsoft Entra tenant, then sign in again. +2. Account settings > User management > Microsoft Entra applications: add an app (any name and reply URL, e.g. `https://localhost`), give it the **Manager** role, then **Add new key**. Copy the client ID and the client secret (shown once). +3. Seller ID: Account settings > Organization profile > Legal info. +4. Repo secrets: `PARTNER_CENTER_TENANT_ID`, `PARTNER_CENTER_SELLER_ID`, `PARTNER_CENTER_CLIENT_ID`, `PARTNER_CENTER_CLIENT_SECRET`. +5. Repo variable `STORE_PUBLISH=true` (set it to `false` to pause the job). +6. Settings > Environments > `microsoft-store`: add yourself as required reviewer so each submission waits for approval. +7. Locally: `msstore reconfigure --tenantId ... --sellerId ... --clientId ... --clientSecret ...`. The interactive form can fail with "Error while retrieving Organization"; the flags work. -Local equivalent: `msstore reconfigure ...`, then `msstore publish -id 9NVSJZ72LTZ3 --noCommit` (draft), `msstore submission get 9NVSJZ72LTZ3`, `msstore submission publish 9NVSJZ72LTZ3`. Run `publish` before editing listing metadata, because it discards a pending draft. +On a `v*` tag the job downloads the built bundle and runs `msstore publish -id 9NVSJZ72LTZ3`, then `msstore submission poll`. The Store re-signs the package, so the self-signed PFX does not matter. Only free apps are supported by the CLI; the version must be higher than the last published one, so bump the version before tagging. A `.msixbundle` path works with `publish` (verified with `--noCommit`). + +Gotchas: + +- The API cannot touch a draft created in the Partner Center web UI. If one is open, `publish` stops on "Ingestion API can only update, delete, and commit submissions that are created through the API", and in CI it would hang. Delete or submit the web draft first, and do not leave drafts open in the portal. +- `publish` discards any existing API draft, so run it before editing listing metadata. +- Never put the client secret in chat, docs, or commits; keep it in the GitHub secret and your password manager. + +Local equivalent: `msstore publish -id 9NVSJZ72LTZ3 --noCommit` (draft), `msstore submission get 9NVSJZ72LTZ3`, `msstore submission publish 9NVSJZ72LTZ3`. `msstore submission delete 9NVSJZ72LTZ3` removes an API draft. ### WinGet