I have two questions about WinGet. First, can individuals submit applications to the public package catalog, and what requirements must an app meet? Second, why does WinGet sometimes fail to show a newer version even after the application's own updater reports that one is available?
3 Answers
Yes. WinGet accepts community contributions. You submit a manifest describing the application, including its version, direct installer URL, package metadata, and silent-install options. The submission is reviewed and tested before it is added. The application does not have to be yours, but it needs a publicly accessible installer and a reliable unattended installation method.
If you mean a private catalog rather than contributing to the public one, WinGet can also use custom sources that follow its REST source format. That requires hosting and maintaining the service yourself, or using a product that provides one. For company-managed applications, organizations may instead choose tools such as Intune or Configuration Manager, depending on their deployment needs.
WinGet's catalog is maintained by publishers and volunteers, so new releases are not necessarily added immediately. Someone has to notice the release, update the manifest, submit it, and wait for validation. The application's built-in updater can therefore offer a version before WinGet knows about it. Anyone interested can help by submitting manifests for missing or outdated releases.
That also explains why paid software deployment catalogs can appear faster: they have staff monitoring vendors and preparing packages, while WinGet relies heavily on community maintenance.