microsoft / microsoft/winget-pkgs

[Package Request]: Microsoft.AppInstaller Development / Release Candidate Builds

Open
#183,597 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Help-Wanted Issue-Feature Package-Request
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

How can we help?

I would like help so I can submit the manifest.

Please read and ensure the following
  • The installer meets the above requirements
Please provide the following information

I would like to have a package for the preview / release candidate / development builds of winget.
However I'm not sure whether Release Candidates, Development Builds and Preview builds should be split up into different packages or should be all together in one package (and what would be the correct package identifier for this case).
Can winget even upgrade itself to an unstable version?

Download Page Url: https://github.com/microsoft/winget-cli/releases/tag/v1.9.2507
Publisher: Microsoft Corporation
Package Name: App Installer ReleaseCandidate / Development
Description: Microsoft App Installer for Windows 10 makes sideloading Windows 10 apps easy: Just double-click the app package, and you won't have to run PowerShell to install apps. App Installer presents the package information like app name, publisher, version, display logo, and the capabilities requested by the app. Get right into the app, no hassles--and if installation doesn't work, the error messages were designed to help you fix the problem. Windows Package Manager is supported through App Installer starting on Windows 10 1809. This application is currently only available for desktop PCs.
Package Version: 1.9.2507
Installer Url: (x86, x64, arm, arm64) https://github.com/microsoft/winget-cli/releases/download/v1.9.2507/Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.msixbundle

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the winget-cli release page linked in the issue and the provided MSIX bundle URL, then check the repository's package-request guidance for how preview, release-candidate, and development builds are represented. Done means determining the package structure and identifier, then submitting the manifest if the request is supported.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.