Windows Package Manager 1.29.70-preview #6130
hackean-msft
announced in
Releases
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
This is a preview build of WinGet for those interested in trying out upcoming features and fixes. While it has had some use and should be free of major issues, it may have bugs or usability problems. If you find any, please help us out by filing an issue.
New in v1.29
New Feature: Source Priority
Note
Experimental under
sourcePriority; defaulted to disabled.With this feature, one can assign a numerical priority to sources when added or later through the
source editcommand. Sources with higher priority are sorted first in the list of sources, which results in them getting put first
in the results if other things are equal.
Tip
Search result ordering in winget is currently based on these values in this order:
Beyond the ability to slightly affect the result ordering, commands that primarily target available packages
(largely
install) will now prefer to use a single result from a source with higher priority rather than prompting fordisambiguation from the user. Said another way, if multiple sources return results but only one of those sources has
the highest priority value (and it returned only one result) then that package will be used rather than giving a
"multiple packages were found" error. This has been applied to both winget CLI and PowerShell module commands.
REST result match criteria update
Along with the source priority change, the results from REST sources (like
msstore) now attempt to correctly set thematch criteria that factor into the result ordering. This will prevent them from being sorted to the top automatically.
Minor Features
--no-progress flag
Added a new
--no-progresscommand-line flag that disables all progress reporting (progress bars and spinners). This flag is universally available on all commands and takes precedence over thevisual.progressBarsetting. Useful for automation scenarios or when running WinGet in environments where progress output is undesirable.Authenticated GitHub API requests in PowerShell module
The PowerShell module now automatically uses
GH_TOKENorGITHUB_TOKENenvironment variables to authenticate GitHub API requests. This significantly increases the GitHub API rate limit, preventing failures in CI/CD pipelines. Use-Verboseto see which token is being used.Bug Fixes
What's Changed
New Contributors
Full Changelog: v1.29.30-preview...v1.29.70-preview
This discussion was created from the release Windows Package Manager 1.29.70-preview.
Beta Was this translation helpful? Give feedback.
All reactions