Windows Package Manager (WinGet) 1.29.70 Preview build for Windows 10 and 11

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 edit command. 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:

1. Match quality (how well a valid field matches the search request)
2. Match field (which field was matched against the search request)
3. Source order (was always relevant, but with priority you can more easily affect this)

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 for disambiguation 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 the match 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-progress command-line flag that disables all progress reporting (progress bars and spinners). This flag is universally available on all commands and takes precedence over the visual.progressBar setting. 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_TOKEN or GITHUB_TOKEN environment variables to authenticate GitHub API requests. This significantly increases the GitHub API rate limit, preventing failures in CI/CD pipelines. Use -Verbose to see which token is being used.

Bug Fixes​

What's Changed​

• Replaced "(C)" with "©" in the main menu. by @DandelionSprout in #5845
• Source priority by @JohnMcPMS in #6029
• Update json vcpkg by @JohnMcPMS in #6039
• Coalesce comments from loc suggestions by @JohnMcPMS in #6033
• Update Roadmap Milestones doc by @Kissaki in #5824
• Add copilot instructions by @JohnMcPMS in #6048
• Add --no-progress option by @JohnMcPMS in #6049
• Remove Crescendo PowerShell by @JohnMcPMS in #6056
• Fix casing of WinGet by @JohnMcPMS in #6059
• Added more info for "Installer Types" values in Settings.md. by @DandelionSprout in #6067
• Diagnostics update and stable DSC for tests by @JohnMcPMS in #6084
• feat: authenticate GitHub API requests using GH_TOKEN/GITHUB_TOKEN by @wmmc88 in #6071
• Tool to investigate SQLite compression by @JohnMcPMS in #6074
• Add dependencies only option by @JohnMcPMS in #6069

New Contributors​

• @DandelionSprout made their first contribution in #5845
• @Kissaki made their first contribution in #5824
• @wmmc88 made their first contribution in #6071

Full Changelog: v1.29.30-preview...v1.29.70-preview




See also: