List view
Features and bugfixes targeted to coincide with [WinGet 1.10](https://github.com/microsoft/winget-cli/milestone/45) The "Due date" is aspirational and primarily intended to help sort Milestones. As the date approaches, features and bugs may be moved to the next milestone. Note: When new schema changes are released in the WinGet client, changes to support new manifest keys will not be rolled out for validation until more than 50% of devices have upgraded to the latest stable version of the client.
Due by March 31, 2025•993/993 issues closedFeatures and bugfixes targeted to coincide with [WinGet 1.9](https://github.com/microsoft/winget-cli/milestone/44) The "Due date" is aspirational and primarily intended to help sort Milestones. As the date approaches, features and bugs may be moved to the next milestone. Note: When new schema changes are released in the WinGet client, changes to support new manifest keys will not be rolled out for validation until more than 50% of devices have upgraded to the latest stable version of the client.
Due by November 30, 2024•279/279 issues closedFeatures and bugfixes targeted to coincide with [WinGet 1.8](https://github.com/microsoft/winget-cli/milestone/43) The "Due date" is aspirational and primarily intended to help sort Milestones. As the date approaches, features and bugs may be moved to the next milestone. Note: When new schema changes are released in the WinGet client, changes to support new manifest keys will not be rolled out for validation until more than 50% of devices have upgraded to the latest stable version of the client.
Due by June 25, 2024•256/256 issues closedFeatures and bugfixes targeted to coincide with [WinGet 1.7](https://github.com/microsoft/winget-cli/milestone/42) The "Due date" is aspirational and primarily intended to help sort Milestones. As the date approaches, features and bugs may be moved to the next milestone. Note: When new schema changes are released in the WinGet client, changes to support new manifest keys will not be rolled out for validation until more than 50% of devices have upgraded to the latest stable version of the client.
Due by February 27, 2024•2825/2826 issues closedFeatures and bugfixes targeted to ship Windows Package Manager v1.3 Pipelines. The "Due date" is aspirational and primarily intended to help sort Milestones As the date approaches features and bugs may be moved to the next milestone.
Due by July 31, 2022•4/4 issues closedFeatures and bugfixes that will be required to ship Windows Package Manager v1.2. The "Due date" is aspirational and primarily intended to help sort Milestones
Due by December 31, 2021•10/10 issues closedFeatures and bugfixes that will be required or coordinated to ship Windows Package Manager v1.1. The "Due date" is aspirational and primarily intended to help sort Milestones
Due by September 30, 2021•13/13 issues closedFeatures and bugfixes that will be required or coordinated to ship Windows Package Manager v1.0. The "Due date" is aspirational and primarily intended to help sort Milestones
Due by May 31, 2021•21/21 issues closedAuto add uninstall installers - The goal for this milestone is to automatically determine the uninstall for a package. The "Due date" is aspirational and primarily intended to help sort Milestones. Issues with "Issue-Bug" label will be optimistically selected and may roll to next milestone.
Due by April 9, 2021Daily scan for updates to "latest" installer & update manifest - The goal for this milestone is to automatically check manifests for "latest" version of packages that point to a vanity URL with an invalid SHA256 and adjust them. The "Due date" is aspirational and primarily intended to help sort Milestones. Issues with "Issue-Bug" label will be optimistically selected and may roll to next milestone.
Due by May 7, 2021•1/1 issues closedAuto add signature SHA256 for MSIX installers - The goal for this milestone is to automatically enrich manifests with the MSIX signature SHA256. The "Due date" is aspirational and primarily intended to help sort Milestones. Issues with "Issue-Bug" label will be optimistically selected and may roll to next milestone.
Due by March 12, 2021Automation for new version - The goal for this milestone is additional automated validations for new versions of packages. The "Due date" is aspirational and primarily intended to help sort Milestones. Issues with "Issue-Bug" label will be optimistically selected and may roll to next milestone.
Due by October 30, 2020•1/1 issues closedFeatures and bugfixes that will be required to ship Windows Package Manager v0.2
No due date•1/1 issues closed