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
Some packages offer a different "latest" version of an application based on the architecture supported.
When the WinGet client is communicating with a REST endpoint the communications should be optimized to deal with different versions for different architectures.
The default flow should provide a better customer experience for both the "install" and "upgrade" scenarios.
When a specific architecture is specified using arguments, the response should honor the architecture specified.
When the "download" flow is being used, there should be an affordance to download the latest versions for "all" architectures.
There may also be caveats when a specific version is requested as opposed to just the "latest" version.
Description of the new feature / enhancement
Some packages offer a different "latest" version of an application based on the architecture supported.
When the WinGet client is communicating with a REST endpoint the communications should be optimized to deal with different versions for different architectures.
The default flow should provide a better customer experience for both the "install" and "upgrade" scenarios.
When a specific architecture is specified using arguments, the response should honor the architecture specified.
When the "download" flow is being used, there should be an affordance to download the latest versions for "all" architectures.
There may also be caveats when a specific version is requested as opposed to just the "latest" version.
Related to:
Proposed technical implementation details
No response
The text was updated successfully, but these errors were encountered: