Template publication automation

[chatasweetie]

Summary of the Pull Request

This PR adds comprehensive publication tooling to the CmdPal extension template, enabling developers to easily publish their extensions to both Microsoft Store and WinGet for the first time.

Still missing:

• public dev docs to accompany this change
• post initial publication github action scripts

PR Checklist

• Closes: CmdPal: Make new extension template instantly publishable to Store #43240

• Communication: I've discussed this with core contributors already. If the work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end-user-facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: Publication docs for updated template with publication scripts MicrosoftDocs/windows-dev-docs#5738

Detailed Description of the Pull Request / Additional comments

Documentation created at MicrosoftDocs/windows-dev-docs#5738

Microsoft Store Publishing

• One-time setup script (one-time-store-pubishing-setup.ps1): Automates configuration of Store-specific settings (Package Identity Name, Publisher Certificate, Display Name, etc.)
• Build automation (build-msix-bundles.ps1): Builds x64 and ARM64 MSIX packages and creates combined .msixbundle files for Store submission
• Resource folder (microsoft-store-resources/): Contains auto-generated bundle_mapping.txt for bundle creation

WinGet Publishing

• One-time setup script (one-time-winget-publishing-setup.ps1): Configures extension for WinGet publishing via EXE installer
• Build script (winget-resources/build-exe.ps1): Builds standalone EXE installer for WinGet distribution
• Inno Setup template (winget-resources/setup-template.iss): Professional installer template with COM registration
• GitHub Actions workflow (winget-resources/release-extension.yml): Automated CI/CD for building and releasing installers

Validation Steps Performed

[github-advanced-security]

check-spelling found more than 20 potential problems in the proposed changes. Check the Files changed tab for more details.

[chatasweetie]

Docs update PR: MicrosoftDocs/windows-dev-docs#5738

[github-actions]

@check-spelling-bot Report

🔴 Please review

See the 📂 files view, the 📜action log, or 📝 job summary for details.

Unrecognized words (1)

WASDK

These words are not needed and should be removed

CLITo CVS Notavailable toolgood Uninitializes wasdk

To accept these unrecognized words as correct and remove the previously acknowledged and now absent words, you could run the following commands

... in a clone of the git@github.com:microsoft/PowerToys.git repository
on the template-automation branch (ℹ️ how do I use this?):

curl -s -S -L 'https://raw.githubusercontent.com/check-spelling/check-spelling/c635c2f3f714eec2fcf27b643a1919b9a811ef2e/apply.pl' |
perl - 'https://github.com/microsoft/PowerToys/actions/runs/20352210426/attempts/1' &&
git commit -m 'Update check-spelling metadata'

Forbidden patterns 🙅 (1)

In order to address this, you could change the content to not match the forbidden patterns (comments before forbidden patterns may help explain why they're forbidden), add patterns for acceptable instances, or adjust the forbidden patterns themselves.

These forbidden patterns matched content:

Should be GitHub

(?<![&*.]|// |\b(?:from|import|type) )\bGithub\b(?![{()])

Errors ❌ (2)

See the 📂 files view, the 📜action log, or 📝 job summary for details.

❌ Errors	Count
❌ check-file-path	1
❌ forbidden-pattern	1

See ❌ Event descriptions for more information.

If the flagged items are 🤯 false positives

If items relate to a ...

• binary file (or some other file you wouldn't want to check at all).

  Please add a file path to the excludes.txt file matching the containing file.

  File paths are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your files.

  ^ refers to the file's path from the root of the repository, so ^README\.md$ would exclude README.md (on whichever branch you're using).

• well-formed pattern.

  If you can write a pattern that would match it,
  try adding it to the patterns.txt file.

  Patterns are Perl 5 Regular Expressions - you can test yours before committing to verify it will match your lines.

  Note that patterns can't match multiline strings.

[niels9001]

@chatasweetie Does this require any more work? This doesn't need to land for 0.97, right?

[michaeljolley]

@chatasweetie, got a conflict to resolve. Anything else need to be done here?