Windows Package Manager v1.1.2.0

[ryfu-msft]

This release includes v1.2 Schema support as well as logic to help generate and update manifests for portable packages. We have also made improvements to address issues when submitting manifests to forked repos that are out of sync with the upstream repository.

Changes:

• 3ea6614 Fix null/empty filename string when downloading package file (Fix null/empty filename string when downloading package file #293)
• 99cc214 Add support for creating and updating portable manifests (Add support for creating and updating portable manifests #290)
• 9963de9 Sync fork prior to creating reference and handle NotFoundException (Sync fork prior to creating reference and handle NotFoundException #289)
• b8b1ab5 always prompt for packageId (Always prompt for package identifier #288)
• 49a1fb4 Add custom YamlDotNet emitter that makes all fields with newlines use literal style. (Add custom YamlDotNet emitter that makes all fields with newlines use literal style. #281)
• 9915d37 Add support for 1.2 Schema (Add support for 1.2 Schema #270)

See More

* d063463 Add SBOM task to build pipelines (#267) * 8928d8c update localization files (#266) * 8827b8d Use AppExecutionAlias in release pipeline (#265) * 375420f Add `.github/fabricbot.json` (#274) * 141ec23 increment version to 1.1 (#276) * bda05d6 update localized strings (#275) * * ea9e220 add newly localized strings (#295)

---

This discussion was created from the release Windows Package Manager v1.1.2.0.

[RuiNtD]

How do portable packages work? I tried specifying a ZIP file as an installer URL, but it just says "Failed to parse the package"