Streamline WinGet Packaging: A Guide to Manifest Creator The Windows Package Manager (WinGet) has transformed how software is installed and managed on Windows. For developers and system administrators, publishing applications to the community repository is the best way to reach users. However, manually writing the YAML manifests required for submissions can be tedious and error-prone.
To solve this, Microsoft developed the WinGet Manifest Creator (wingetcreate). This powerful command-line tool automates the creation, updating, and submission of app manifests. Here is how you can use it to streamline your packaging workflow. Why Use WinGet Manifest Creator?
Manually authoring YAML files requires exact formatting and precise metadata, including URLs, installers, architecture types, and version strings. The Manifest Creator removes this friction by:
Extracting Metadata automatically: It parses your installer file (MSI, MSIX, or EXE) to pull product names, publishers, and versions.
Enforcing Validation: It ensures your manifest matches the latest schema before submission.
Integrating GitHub: It can automatically fork the WinGet repository, create a branch, and submit a Pull Request on your behalf. Setting Up the Tool
Before you begin, you need to install the tool and authenticate your GitHub account so it can submit packages for you.
Install WinGetCreate: Run the following command in PowerShell or Command Prompt: powershell winget install Microsoft.WingetCreate Use code with caution.
Generate a GitHub Token: Visit GitHub and create a Personal Access Token (classic) with repo scope. Authenticate: Submit your token to the tool by running: powershell wingetcreate token Use code with caution. Step-by-Step: Creating a New Manifest
The easiest way to build a manifest from scratch is using the interactive wizard. Step 1: Launch the Wizard
Run the new command and provide a direct download link to your application’s installer file: powershell wingetcreate new https://example.com Use code with caution. Step 2: Fill in the Blanks
The tool will download your installer, analyze it, and prompt you to fill in missing information through a series of command-line prompts. You will need to verify or provide:
PackageIdentifier: The unique ID (Format: Publisher.Application). PackageVersion: The current software version. DefaultLocale: Typically en-US. ShortDescription: A brief summary of what your app does. Step 3: Review and Submit
Once all fields are complete, the tool clones the microsoft/winget-pkgs repository locally, validates your new YAML files, and asks if you want to submit. Selecting “Yes” automatically pushes the files to GitHub and opens a Pull Request. Updating Existing Packages
Software changes frequently, but updating your WinGet manifest does not require starting over. The Manifest Creator features an update command specifically for new releases. To update an existing package, run: powershell
wingetcreate update Publisher.Application –version 2.0.0 –urls https://example.com Use code with caution.
This command downloads the new installer, extracts the updated cryptographic SHA256 hash, updates the version metadata, and prepares the submission immediately. Automating with CI/CD Pipelines
For development teams, the true power of WinGet Manifest Creator lies in automation. You can integrate wingetcreate into your GitHub Actions or Azure DevOps pipelines. By passing arguments like –token, –interactive false, and –submit, your pipeline can automatically publish every new software release straight to the WinGet repository without human intervention. Conclusion
The WinGet Manifest Creator bridges the gap between compiling your software and delivering it to millions of Windows users. By automating metadata extraction and GitHub repository management, it turns what used to be a multi-step chore into a single command-line execution. To tailor this guide for your project, let me know:
Leave a Reply