GeezerVisonThe World Wide Web, restored to 800 pixels of glory. | ||||||||||||||||||||||||||||||||||||||||
| Home|About|Gaming cabinet|Archives|How it works|Starter sites | ||||||||||||||||||||||||||||||||||||||||
GeezerVison is showing github.com — Releases · microsoft/winget-cli Releases · microsoft/winget-cli
Windows Package Manager 1.29.380000f6b5
This commit was created on GitHub.com and signed with GitHub’s verified signature.
This is a servicing release of Windows Package Manager v1.29. If you find any bugs or problems, please help us out by filing an issue. New in v1.29New Feature: Source PriorityNote Experimental under With this feature, one can assign a numerical priority to sources when added or later through the 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 REST result match criteria updateAlong with the source priority change, the results from REST sources (like Minor FeaturesPreserve installer arguments across export and import
--no-progress flagAdded a new MCP
|
| Setting | Description |
|---|---|
| manifest | Uses the name of the manifest and a timestamp. Has the same behavior as WinGet 1.28 |
| timestamp | The log name is just a timestamp |
| guid | The log name is a GUID |
| shortguid | The log name is the first 8 characters of a GUID |
list outputwinget list now supports sorting results via --sort <field> (repeatable for multi-field sorting), --ascending/--descending direction flags, and a persistent output.sortOrder setting. Available sort fields: name, id, version, source, available, relevance. By default, results are sorted alphabetically by name when no query is present; use --sort relevance to preserve the previous source-determined ordering.
winget export now works when the destination path is a hidden fileuseLatest property in the DSC v3 Microsoft.WinGet/Package resource schema to emit a boolean default (false) instead of the incorrect string "false".SignFile in WinGetSourceCreator now supports an optional RFC 3161 timestamp server via the new TimestampServer property on the Signature model. When set, signtool.exe is called with /tr <url> /td sha256, embedding a countersignature timestamp so that signed packages remain valid after the signing certificate expires.signtool.exe and makeappx.exe are now quoted, fixing failures when paths contain spaces.winget validate now performs case-insensitive comparison for file extensions where applicablewinget source reset now properly resets default sources instead of removing themMicrosoft.WinGet/Package resource now honors the installMode property to use silent or interactive installer switches as specified0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.Full Changelog: v1.29.290...v1.29.380
There was an error while loading. Please reload this page.
28ca400 This is a servicing release of Windows Package Manager v1.30. If you find any bugs or problems, please help us out by filing an issue.
--ignore-unavailable flag for installAdded a new --ignore-unavailable flag to the install command. When installing multiple packages, this flag allows the operation to continue with the remaining packages instead of failing entirely when one or more packages are not found in the configured sources. This brings the same behavior previously available with import --ignore-unavailable to direct multi-package installs.
winget search --id <msstoreId> could fail to return a Microsoft Store package unless --exact was also provided.0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.Full Changelog: v1.30.100-preview...v1.30.140-preview
There was an error while loading. Please reload this page.
4638f90 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.
--ignore-unavailable flag for installAdded a new --ignore-unavailable flag to the install command. When installing multiple packages, this flag allows the operation to continue with the remaining packages instead of failing entirely when one or more packages are not found in the configured sources. This brings the same behavior previously available with import --ignore-unavailable to direct multi-package installs.
0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.--ignore-unavailable option to install command by CatBraaain in #6351Full Changelog: v1.30.90-preview...v1.30.100-preview
There was an error while loading. Please reload this page.
4e87530 This is a servicing release of Windows Package Manager v1.29. If you find any bugs or problems, please help us out by filing an issue.
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:
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.
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.
winget export now captures the --override and --custom arguments that were used when a package was originally installed and saves them into the export file. When subsequently running winget import, those values are automatically re-applied during installation — --override replaces all installer arguments and --custom appends extra switches — so packages can be reinstalled with the same customizations without any manual intervention. Both fields are optional and independent of each other; packages without stored installer arguments are unaffected.
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.
upgrade supportThe WinGet MCP server's existing tools have been extended with new parameters to support upgrade scenarios:
find-winget-packages now accepts an upgradeable parameter (default: false). When set to true, it lists only installed packages that have available upgrades — equivalent to winget upgrade. The query parameter becomes optional in this mode, allowing it to filter results or be omitted to list all upgradeable packages. AI agents can use this to answer requests like "What apps can I update with WinGet?"install-winget-package now accepts an upgradeOnly parameter (default: false). When set to true, it only upgrades an already-installed package and returns a clear error if the package is not installed (pointing to install-winget-package without upgradeOnly instead). AI agents can use this to answer requests like "Update WinGetCreate" or, in combination with find-winget-packages with upgradeable=true, "Update all my apps."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.
Installer type selection no longer depends on the order defined on the manifest. Instead, preference is given in this order:
When a user configures installer type requirements or preferences, the order in which they are listed is now respected during installer selection.
list output when redirectedwinget list (and similar table commands) no longer truncates output when stdout is redirected to a file or variable — column widths are now computed from the full result set.Added a user setting (logging.fileNameStrategy) for controlling the default naming strategy for installer log files. Supported values are manifest (default), timestamp, guid, and shortguid. Only applies to logs generated by installers if the installer itself supports the logging switch / parameter.
| Setting | Description |
|---|---|
| manifest | Uses the name of the manifest and a timestamp. Has the same behavior as WinGet 1.28 |
| timestamp | The log name is just a timestamp |
| guid | The log name is a GUID |
| shortguid | The log name is the first 8 characters of a GUID |
list outputwinget list now supports sorting results via --sort <field> (repeatable for multi-field sorting), --ascending/--descending direction flags, and a persistent output.sortOrder setting. Available sort fields: name, id, version, source, available, relevance. By default, results are sorted alphabetically by name when no query is present; use --sort relevance to preserve the previous source-determined ordering.
winget export now works when the destination path is a hidden fileuseLatest property in the DSC v3 Microsoft.WinGet/Package resource schema to emit a boolean default (false) instead of the incorrect string "false".SignFile in WinGetSourceCreator now supports an optional RFC 3161 timestamp server via the new TimestampServer property on the Signature model. When set, signtool.exe is called with /tr <url> /td sha256, embedding a countersignature timestamp so that signed packages remain valid after the signing certificate expires.signtool.exe and makeappx.exe are now quoted, fixing failures when paths contain spaces.winget validate now performs case-insensitive comparison for file extensions where applicablewinget source reset now properly resets default sources instead of removing themMicrosoft.WinGet/Package resource now honors the installMode property to use silent or interactive installer switches as specified0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.Full Changelog: v1.29.280...v1.29.290
There was an error while loading. Please reload this page.
12dad5c 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.
Nothing yet.
0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.Full Changelog: v1.30.80-preview...v1.30.90-preview
There was an error while loading. Please reload this page.
b042bf9 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.
Nothing yet.
0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.Full Changelog: v1.30.50-preview...v1.30.80-preview
There was an error while loading. Please reload this page.
6b3bc96 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.
Nothing yet.
0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.Full Changelog: v1.29.240...v1.30.70-preview
6b3bc96 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.
Nothing yet.
0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.Full Changelog: v1.29.240...v1.30.50-preview
There was an error while loading. Please reload this page.
fe424a1 This is the latest of Windows Package Manager v1.29. If you find any bugs or problems, please help us out by filing an issue.
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:
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.
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.
winget export now captures the --override and --custom arguments that were used when a package was originally installed and saves them into the export file. When subsequently running winget import, those values are automatically re-applied during installation — --override replaces all installer arguments and --custom appends extra switches — so packages can be reinstalled with the same customizations without any manual intervention. Both fields are optional and independent of each other; packages without stored installer arguments are unaffected.
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.
upgrade supportThe WinGet MCP server's existing tools have been extended with new parameters to support upgrade scenarios:
find-winget-packages now accepts an upgradeable parameter (default: false). When set to true, it lists only installed packages that have available upgrades — equivalent to winget upgrade. The query parameter becomes optional in this mode, allowing it to filter results or be omitted to list all upgradeable packages. AI agents can use this to answer requests like "What apps can I update with WinGet?"install-winget-package now accepts an upgradeOnly parameter (default: false). When set to true, it only upgrades an already-installed package and returns a clear error if the package is not installed (pointing to install-winget-package without upgradeOnly instead). AI agents can use this to answer requests like "Update WinGetCreate" or, in combination with find-winget-packages with upgradeable=true, "Update all my apps."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.
Installer type selection no longer depends on the order defined on the manifest. Instead, preference is given in this order:
When a user configures installer type requirements or preferences, the order in which they are listed is now respected during installer selection.
list output when redirectedwinget list (and similar table commands) no longer truncates output when stdout is redirected to a file or variable — column widths are now computed from the full result set.Added a user setting (logging.fileNameStrategy) for controlling the default naming strategy for installer log files. Supported values are manifest (default), timestamp, guid, and shortguid. Only applies to logs generated by installers if the installer itself supports the logging switch / parameter.
| Setting | Description |
|---|---|
| manifest | Uses the name of the manifest and a timestamp. Has the same behavior as WinGet 1.28 |
| timestamp | The log name is just a timestamp |
| guid | The log name is a GUID |
| shortguid | The log name is the first 8 characters of a GUID |
list outputwinget list now supports sorting results via --sort <field> (repeatable for multi-field sorting), --ascending/--descending direction flags, and a persistent output.sortOrder setting. Available sort fields: name, id, version, source, available, relevance. By default, results are sorted alphabetically by name when no query is present; use --sort relevance to preserve the previous source-determined ordering.
winget export now works when the destination path is a hidden fileuseLatest property in the DSC v3 Microsoft.WinGet/Package resource schema to emit a boolean default (false) instead of the incorrect string "false".SignFile in WinGetSourceCreator now supports an optional RFC 3161 timestamp server via the new TimestampServer property on the Signature model. When set, signtool.exe is called with /tr <url> /td sha256, embedding a countersignature timestamp so that signed packages remain valid after the signing certificate expires.signtool.exe and makeappx.exe are now quoted, fixing failures when paths contain spaces.winget validate now performs case-insensitive comparison for file extensions where applicablewinget source reset now properly resets default sources instead of removing themMicrosoft.WinGet/Package resource now honors the installMode property to use silent or interactive installer switches as specified0x8000ffff) when using --disable-interactivity with the Resume experimental feature enabled during install operations.Full Changelog: v1.29.250...v1.29.280
There was an error while loading. Please reload this page.
2f4f2cf This is a release candidate of Windows Package Manager v1.29. If you find any bugs or problems, please help us out by filing an issue.
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:
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.
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.
winget export now captures the --override and --custom arguments that were used when a package was originally installed and saves them into the export file. When subsequently running winget import, those values are automatically re-applied during installation — --override replaces all installer arguments and --custom appends extra switches — so packages can be reinstalled with the same customizations without any manual intervention. Both fields are optional and independent of each other; packages without stored installer arguments are unaffected.
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.
upgrade supportThe WinGet MCP server's existing tools have been extended with new parameters to support upgrade scenarios:
find-winget-packages now accepts an upgradeable parameter (default: false). When set to true, it lists only installed packages that have available upgrades — equivalent to winget upgrade. The query parameter becomes optional in this mode, allowing it to filter results or be omitted to list all upgradeable packages. AI agents can use this to answer requests like "What apps can I update with WinGet?"install-winget-package now accepts an upgradeOnly parameter (default: false). When set to true, it only upgrades an already-installed package and returns a clear error if the package is not installed (pointing to install-winget-package without upgradeOnly instead). AI agents can use this to answer requests like "Update WinGetCreate" or, in combination with find-winget-packages with upgradeable=true, "Update all my apps."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.
Installer type selection no longer depends on the order defined on the manifest. Instead, preference is given in this order:
When a user configures installer type requirements or preferences, the order in which they are listed is now respected during installer selection.
list output when redirectedwinget list (and similar table commands) no longer truncates output when stdout is redirected to a file or variable — column widths are now computed from the full result set.Added a user setting (logging.fileNameStrategy) for controlling the default naming strategy for installer log files. Supported values are manifest (default), timestamp, guid, and shortguid. Only applies to logs generated by installers if the installer itself supports the logging switch / parameter.
| Setting | Description |
|---|---|
| manifest | Uses the name of the manifest and a timestamp. Has the same behavior as WinGet 1.28 |
| timestamp | The log name is just a timestamp |
| guid | The log name is a GUID |
| shortguid | The log name is the first 8 characters of a GUID |
list outputwinget list now supports sorting results via --sort <field> (repeatable for multi-field sorting), --ascending/--descending direction flags, and a persistent output.sortOrder setting. Available sort fields: name, id, version, source, available, relevance. By default, results are sorted alphabetically by name when no query is present; use --sort relevance to preserve the previous source-determined ordering.
winget export now works when the destination path is a hidden fileuseLatest property in the DSC v3 Microsoft.WinGet/Package resource schema to emit a boolean default (false) instead of the incorrect string "false".SignFile in WinGetSourceCreator now supports an optional RFC 3161 timestamp server via the new TimestampServer property on the Signature model. When set, signtool.exe is called with /tr <url> /td sha256, embedding a countersignature timestamp so that signed packages remain valid after the signing certificate expires.signtool.exe and makeappx.exe are now quoted, fixing failures when paths contain spaces.winget validate now performs case-insensitive comparison for file extensions where applicablewinget source reset now properly resets default sources instead of removing themMicrosoft.WinGet/Package resource now honors the installMode property to use silent or interactive installer switches as specified
There was an error while loading. Please reload this page.