winget-create
winget-cli-restsource
Our great sponsors
winget-create | winget-cli-restsource | |
---|---|---|
3 | 5 | |
449 | 231 | |
2.4% | 4.3% | |
8.2 | 5.5 | |
9 days ago | 14 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
winget-create
-
Automatically upgrade your package on winget with GitHub Actions
This workflow uses Windows Package Manager Manifest Creator to update and submit a new version of a package manifest
-
Announcing Windows Package Manager 1.1
Yes, any installer (MSIX, MSI, EXE) may be added (https://github.com/microsoft/winget-pkgs). There is even a new tool the Windows Package Manager Manifest Creator (https://github.com/microsoft/winget-create) to make it easier to build a manifest and submit it to the GitHub repository. Portable / Stanalone .exe files and .zip files aren't supported yet, but they are on the backlog.
-
Windows Package Manager 1.0
You can also add your programs or packages by executing winget install wingetcreate to install the Windows Package Manager Manifest Creator. Once the tool has been installed, execute wingetcreate new provide the URL to the installer. Then the tool will download the installer, parse it to determine any of the manifest values available in the installer, and guide you through the process to generate a valid manifest. If you provide your GitHub credentials when prompted, it will even fork the repository, create a new branch, submit a pull request, and provide you the URL to track its progress.
winget-cli-restsource
-
winget-cli-restsource VS WinGetty - a user suggested alternative
2 projects | 9 Jul 2023
- how to solve winget source add error
-
In case you don't like Edge, here's how to avoid it. (Even if you do like Edge, this might still be useful)
There is a way to point it to custom repositories, here's the documentation for that. They even have a repo with a template for hosting your own rest source here.
-
Announcing Windows Package Manager 1.1
You can also stand up a private source. We have a reference implementation at https://github.com/microsoft/winget-cli-restsource. It's a bit tough to deploy presently, but we're making investments there. A PR is in progress with some PowerShell to make it easier to deploy.
-
Windows Package Manager 1.0
Last but not least, They also released a reference implementation for the REST API source so you can host your private repository. This is a new type of source for the Windows Package Manager. The default source is a “PreIndexed” Package delivered via the Microsoft Store, but now you may add additional REST-based sources if they properly implement the JSON-based REST API schema.
What are some alternatives?
Chocolatey - Chocolatey - the package manager for Windows
winget-pkgs - The Microsoft community Windows Package Manager manifest repository
Winget-AutoUpdate - WAU daily updates apps as system and notify connected users. (Allowlist and Blocklist support)
rewinged - rewinged is a self-hosted winget package source
appget - Free and open package manager for Windows.
winget-cli - WinGet is the Windows Package Manager. This project includes a CLI (Command Line Interface), PowerShell modules, and a COM (Component Object Model) API (Application Programming Interface).
Winget-Install - Powershell scripts for Winget with SCCM/Intune
WinGetty - An open source REST Backend for creating a private WinGet Repo without any cloud dependency.
FSL - A Package Manager.
winstall - A web app for browsing and installing Windows Package Manager apps.
nushell - A new type of shell