You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 14, 2026. It is now read-only.
This repository was archived by the owner on Jan 14, 2026. It is now read-only.
The winget PowerShell commandlets now use C#, so I should add an option for people to use them instead of my own code where available (mainly when getting the list of available packages, which would be way faster and I should be able to still get manifests somehow, or at least the descriptions and most-used parts of the manifests, out of another command). #167
This is in a recent winget 1.5 release: https://github.com/microsoft/winget-cli/releases/tag/v1.5.1572 . Using the PowerShell commandlets will be optional where possible, but some more-complicated features may require them as otherwise I'd have to parse text, and I don't want to do that. Will keep the code that doesn't use the PowerShell commandlets around for both compatibility and just if people don't want to use/have trouble with the PowerShell commandlets, though.
This is in a recent winget 1.5 release: https://github.com/microsoft/winget-cli/releases/tag/v1.5.1572 . Using the PowerShell commandlets will be optional where possible, but some more-complicated features may require them as otherwise I'd have to parse text, and I don't want to do that. Will keep the code that doesn't use the PowerShell commandlets around for both compatibility and just if people don't want to use/have trouble with the PowerShell commandlets, though.