soredake · pull · Jul 28, 2026 · Jul 27, 2026 · Jul 27, 2026 · Jul 27, 2026
diff --git a/doc/Authoring.md b/doc/Authoring.md
@@ -103,7 +103,7 @@ winget settings --enable LocalManifestFiles
 winget install --manifest <path>
 ```
 
-For a more isolated test, use the [SandboxTest.ps1 Script](https://github.com/microsoft/winget-pkgs/blob/master/doc/tools/SandboxTest.md) to test in Windows Sandbox.
+For a more isolated test, use the [SandboxTest.ps1 Script](tools/SandboxTest.md) to test in Windows Sandbox.
 
 ## Advanced Authoring
 
@@ -175,7 +175,7 @@ When comparing one `Part` to another, WinGet goes through the following process.
 	* If both values of `string` are empty, the parts are equal
 	* If one `Part` has a value in `string` and the other does not, the `Part` which ***does not*** have a value in `string` is considered to be greater
 	* Example: When comparing `34` and `34-beta`, the `integer` is equal for both (`34`). However, the `string` for the former is empty and the `string` for the latter is `-beta`, so `34` is the larger `Part`. This leads to `1.2.34` being considered a higher `Version` than `1.2.34-beta`
-4. If both parts have a value in `string`, perform a case-insensitive comparison of the two
+3. If both parts have a value in `string`, perform a case-insensitive comparison of the two
 	* If the values of `string` are not equal, the lexicographic comparison determines which `Part` is larger
 
 #### Examples of Version Comparisons

diff --git a/doc/FAQ.md b/doc/FAQ.md
@@ -12,7 +12,7 @@
   10. [**How can I use PowerShell to parse the output from winget?**](#how-can-i-use-powershell-to-parse-the-output-from-winget)
   11. [**Why do WinGet and AppInstaller have different versions?**](#why-do-winget-and-appinstaller-have-different-versions)
   12. [**How do I know the packages in the Community Repository are safe?**](#how-do-i-know-the-packages-in-the-community-repository-are-safe)
-  13. [**How do portable applications get “Installed”?**](#how-do-portable-applications-get-installed)
+  13. [**How do portable applications get "Installed"?**](#how-do-portable-applications-get-installed)
 -----
 ## **What is an ARP Entry?**
 ARP stands for `A`dd and `R`emove `P`rograms. In Windows, installer files put information about the package they have installed into the Windows Registry. This information is used to tell Windows exactly what a program is and how to uninstall or modify it. Users can view these entries through the Add and Remove Programs option in Control Panel, or by running `appwiz.cpl`. Alternatively, the `Apps & features` menu in Windows Settings can be used to view the entries. Each entry in the table is an ARP Entry, and the Windows Package Manager uses these entries to help determine which applications are currently installed on your system.
@@ -68,13 +68,17 @@ Applications may continually upgrade due to the following reasons:
 ### Future Work:
 Efforts to resolve these issues are being tracked in:
 - [microsoft/winget-cli#2345](https://github.com/microsoft/winget-cli/issues/2345)
-- [microsoft/winget-cli#1413](https://github.com/microsoft/winget-cli/issues/1413)
+
 ## **How can I use PowerShell to parse the output from winget?**
-The Windows Package Manager is still in development and does not yet support emitting rich data objects as output. There are a few issues tracking this feature request. Please add your thumbs up to these issues as the reactions are used to help prioritize which features are implemented next.
-* [Add Native PowerShell Support - microsoft/winget-cli#221](https://github.com/microsoft/winget-cli/issues/221)
-* [Add list option to format output as JSON - microsoft/winget-cli#2032](https://github.com/microsoft/winget-cli/issues/2032)
+Native PowerShell support is now available through the `Microsoft.WinGet.Client` module on the [PowerShell Gallery](https://www.powershellgallery.com/packages/Microsoft.WinGet.Client). It provides PowerShell cmdlets that return structured objects, making it straightforward to use WinGet in scripts and automation without parsing text output.
+
+Install the module with:
+
+```powershell
+Install-Module -Name Microsoft.WinGet.Client
+```
 
-Also, take a look at the [discussions](https://github.com/microsoft/winget-cli/discussions/categories/powershell) based around PowerShell support!
+Take a look at the [discussions](https://github.com/microsoft/winget-cli/discussions/categories/powershell) for community examples and Q&A around PowerShell support.
 ## Why do WinGet and AppInstaller have different versions?
 
 WinGet and AppInstaller are two distinct pieces of software, even though WinGet is included as part of the AppInstaller package. Their versioning differs because:

diff --git a/doc/FirstContribution.md b/doc/FirstContribution.md
@@ -10,7 +10,7 @@ Use this checklist before you open your first manifest PR to `microsoft/winget-p
 4. Use a [supported installer type](Policies.md#installer-types) and make sure the installer can run unattended.
 5. Use a multi-file manifest set. Singleton manifests are not allowed in the community repository.
 6. Add schema headers to every manifest file, including the `# yaml-language-server: $schema=...` comment at the top of each file.
-7. Use the latest manifest version supported by the repository. See [doc\manifest\README.md](manifest/README.md) for the current schema versions.
+7. Use the latest manifest version supported by the repository. See [doc/manifest/README.md](manifest/README.md) for the current schema versions.
 8. Use a stable, version-specific installer URL from an official source whenever possible.
 9. Validate the manifest locally:
 

diff --git a/doc/Moderation.md b/doc/Moderation.md
@@ -129,7 +129,7 @@ Occasionally the automatic validation runs into an issue which is transient, or
 
 > Trigger: Comment `[Policy] reset feedback` on a pull request
 
-The bots which help keep the repository clean sometimes make mistakes or or sometimes a moderator misclicks and accidentally requests changes. This can add the `Needs-Author-Feedback` or `Needs-Attention` labels to pull requests that don't need them. Moderators can remove these labels without re-running the pipelines to allow for the PR to be re-reviewed and merged.
+The bots which help keep the repository clean sometimes make mistakes or sometimes a moderator misclicks and accidentally requests changes. This can add the `Needs-Author-Feedback` or `Needs-Attention` labels to pull requests that don't need them. Moderators can remove these labels without re-running the pipelines to allow for the PR to be re-reviewed and merged.
 
 ### Removing Labels
 

diff --git a/doc/Policies.md b/doc/Policies.md
@@ -8,6 +8,7 @@ Manifests submitted to the community repository are subject to [moderation](Mode
 ## Installer Types
 WinGet supports the following installer types:
 - **MSIX**
+- **APPX**
 - **MSI**
 - **Exe-based installers**
 - **Font files**

diff --git a/doc/README.md b/doc/README.md
@@ -11,15 +11,15 @@ A few different tools are available to help you author a manifest.
 
 If this is your first manifest submission, start with the [first-time contributor checklist](FirstContribution.md).
 
-> [!Note]
+> [!NOTE]
 > Only one package version (one multi-file manifest set) may be submitted per PR.
 > Non-manifest changes such as `README.md`, `doc/`, spelling updates, and tooling updates must be submitted in a separate PR.
 
 ## Testing a Manifest
 
 Now that you have authored your manifest, you should make sure it works as expected.
 
-> [!Note]
+> [!NOTE]
 > You will need to run `winget settings --enable LocalManifestFiles` in an administrative shell before working with local manifests.
 
 ### Locally
@@ -60,7 +60,7 @@ To submit a package to this repository, you should follow these steps:
 5. [Submit](#submit-your-pr) your pull request (PR).
 6. Respond to any feedback in your PR.
 
-> [!Note]
+> [!NOTE]
 > Please check the package's manifest you intend to submit does not already exist in the repository, and there are no open PRs for it in order to avoid duplicates.
 
 ## Submit your PR
@@ -75,16 +75,16 @@ Your PR must be limited to a single package version. If you also need to update
 
 ### Validation Process
 
-Your PR will go through a validation process. The core team or the Microsoft bot (BOT) will use  [labels](https://docs.microsoft.com/windows/package-manager/package/winget-validation#pull-request-labels)  to assist during the process. In case of a failure, the BOT will suggest the problem with the submission and assign the PR back to you.
+Your PR will go through a validation process. The core team or the Microsoft bot (BOT) will use [labels](https://docs.microsoft.com/windows/package-manager/package/winget-validation#pull-request-labels) to assist during the process. In case of a failure, the BOT will suggest the problem with the submission and assign the PR back to you.
 
 #### Community Repository Policies
 
 The WinGet community repository has a set of policies restricting the use of certain manifest fields in PRs. These policies primarily affect optional metadata fields restricted to verified developers. Some fields are automatically populated during our validation process like the fields for icons.
->[!Note]
->The verified developer workflow is still in progress.
+> [!NOTE]
+> The verified developer workflow is still in progress.
 
 ### Respond to PR feedback
 
-If your PR has been assigned to you, a timer will be triggered. You will have 7 days to resolve the issue, or the BOT will automatically close the PR.
+If your PR has been assigned to you, a timer will be triggered. If there is no activity for 5 days, a `No-Recent-Activity` label will be added. If there is still no activity after a further 3 days, the PR will be automatically closed.
 
 Submissions to the repository are reviewed by Windows Package Manager administrators and/or community moderators. These individuals are identified in [Moderation](Moderation.md#moderators).
diff --git a/doc/ValidationFailureGuide.md b/doc/ValidationFailureGuide.md
@@ -5,7 +5,7 @@ When you submit a pull request to [microsoft/winget-pkgs](https://github.com/mic
 > [!TIP]
 > Many issues can be caught before submitting by running:
 > ```powershell
-> winget validate <path-to-manifest>
+> winget validate --manifest <path-to-manifest>
 > winget install --manifest <path-to-manifest>
 > ```
 > For isolated testing, use the [SandboxTest.ps1](https://github.com/microsoft/winget-pkgs/blob/master/doc/tools/SandboxTest.md) script or Windows Sandbox.
@@ -37,7 +37,7 @@ These labels track the progress of your PR through the validation pipeline.
 |---|---|
 | **Azure-Pipeline-Passed** | Your manifest passed automated testing. There may be additional manual verification required. |
 | **Validation-Completed** | All checks passed. Your PR may be merged automatically after moderator review. |
-| **Needs-Author-Feedback** | Something needs your attention. If not addressed within 10 days, the PR will be auto-closed. |
+| **Needs-Author-Feedback** | Something needs your attention. If not addressed within 5 days, `No-Recent-Activity` will be added. If there is still no activity after a further 3 days, the PR will be automatically closed. |
 | **Needs-Attention** | The PR has been escalated to the WinGet engineering team for investigation. |
 | **Blocking-Issue** | The PR cannot be approved until the blocking issue (indicated by an accompanying error label) is resolved. |
 | **Needs-CLA** | You have not signed the [Contributor License Agreement](https://cla.opensource.microsoft.com/microsoft/winget-pkgs). The PR cannot be merged until the CLA is signed. |

diff --git a/doc/tools/Build-MinWinVHD.md b/doc/tools/Build-MinWinVHD.md
@@ -1,6 +1,6 @@
-# Using Build-MinWin11.ps1
+# Using Build-MinWinVHD.ps1
 
-The [Build-MinWinVHD.ps1](Tools/Build-MinWinVHD.ps1) script creates a new `V`irtual `H`ard `D`isk (VHD) using a mounted Windows ISO for use with a virtual machine. This image will have as few dependencies and apps enabled as possible, to provide the best approximation of the images uses by the validation pipelines. Although this is not the same image, it should be close enough to use for testing manifests for those who are unable to use Windows Sandbox and [SandboxTest.ps1](doc/tools/SandboxTest.ps1).
+The [Build-MinWinVHD.ps1](Build-MinWinVHD.ps1) script creates a new `V`irtual `H`ard `D`isk (VHD) using a mounted Windows ISO for use with a virtual machine. This image will have as few dependencies and apps enabled as possible, to provide the best approximation of the images uses by the validation pipelines. Although this is not the same image, it should be close enough to use for testing manifests for those who are unable to use Windows Sandbox and [SandboxTest.ps1](SandboxTest.md).
 
 ## Summary
 

diff --git a/doc/tools/YamlCreate.md b/doc/tools/YamlCreate.md
@@ -1,5 +1,5 @@
 # Using YamlCreate.ps1
-Using the YamlCreate script is easy. First, [create a fork](https://docs.github.com/get-started/quickstart/fork-a-repo) of this repository and then [clone it](https://docs.github.com/repositories/creating-and-managing-repositories/cloning-a-repository) to your computer. Once the repository has finished cloning, open file explorer and navigate to the folder that the repository was cloned into. Inside this folder, you should be able to navigate to the `Tools` folder, which contains the script. Right click on "YamlCreate" and select "Run with PowerShell". If it is your first time running the script, you may see a message that it is installing some additional packages - [NuGet](https://docs.microsoft.com/nuget/), and [powershell-yaml](https://www.powershellgallery.com/packages/powershell-yaml/0.4.2) ([See it on GitHub](https://github.com/cloudbase/powershell-yaml)). These are required for the script to run.
+Using the YamlCreate script is easy. First, [create a fork](https://docs.github.com/get-started/quickstart/fork-a-repo) of this repository and then [clone it](https://docs.github.com/repositories/creating-and-managing-repositories/cloning-a-repository) to your computer. Once the repository has finished cloning, open file explorer and navigate to the folder that the repository was cloned into. Inside this folder, you should be able to navigate to the `Tools` folder, which contains the script. Right click on "YamlCreate" and select "Run with PowerShell". If it is your first time running the script, you may see a message that it is installing some additional packages - [NuGet](https://docs.microsoft.com/nuget/), and [powershell-yaml](https://www.powershellgallery.com/packages/powershell-yaml) ([See it on GitHub](https://github.com/cloudbase/powershell-yaml)). These are required for the script to run.
 
 Once the script begins, it will walk you through a series of prompts to create manifests. Enter the requested information for each of the prompts and once all the prompts are completed, the manifest will be generated! If you have Windows Sandbox enabled and the GitHub CLI installed, you can even automatically test and submit your manifest instead of having to do it manually.
 
@@ -83,5 +83,5 @@ EnableDeveloperOptions: false
 
 # This setting allows for the selection of which manifest version is used
 # The script is not tested with all manifest versions, and stability is not guaranteed. Use with caution
-OverrideManifestVersion: 1.4.0
+OverrideManifestVersion: 1.28.0
 ```
diff --git a/manifests/9/9001/copyparty/1.20.19/9001.copyparty.installer.yaml b/manifests/9/9001/copyparty/1.20.19/9001.copyparty.installer.yaml
@@ -0,0 +1,17 @@
+# Created with YamlCreate.ps1 Dumplings Mod
+# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.12.0.schema.json
+
+PackageIdentifier: 9001.copyparty
+PackageVersion: 1.20.19
+InstallerType: portable
+InstallModes:
+- interactive
+- silent
+UpgradeBehavior: install
+ReleaseDate: 2026-07-27
+Installers:
+- Architecture: x64
+  InstallerUrl: https://github.com/9001/copyparty/releases/download/v1.20.19/copyparty.exe
+  InstallerSha256: 0BAB2B8EC1FC31220F138DE5DEEFC27BBC14D9977F66F00B608BE1DF78D5FBBC
+ManifestType: installer
+ManifestVersion: 1.12.0
diff --git a/manifests/9/9001/copyparty/1.20.19/9001.copyparty.locale.en-US.yaml b/manifests/9/9001/copyparty/1.20.19/9001.copyparty.locale.en-US.yaml
@@ -0,0 +1,63 @@
+# Created with YamlCreate.ps1 Dumplings Mod
+# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.12.0.schema.json
+
+PackageIdentifier: 9001.copyparty
+PackageVersion: 1.20.19
+PackageLocale: en-US
+Publisher: ocv.me
+PublisherUrl: https://github.com/9001/copyparty
+PublisherSupportUrl: https://github.com/9001/copyparty/issues
+Author: "9001"
+PackageName: copyparty
+PackageUrl: https://github.com/9001/copyparty/releases/tag/v1.19.17
+License: MIT
+LicenseUrl: https://github.com/9001/copyparty/blob/HEAD/LICENSE
+Copyright: 2026, ed
+ShortDescription: Portable file server with accelerated resumable uploads, dedup, WebDAV, FTP, TFTP, zeroconf, media indexer, thumbnails++ all in one file, no deps
+Description: Portable file server with accelerated resumable uploads, dedup, WebDAV, FTP, TFTP, zeroconf, media indexer, thumbnails++ all in one file, no deps
+Tags:
+- copyparty
+- file-server
+- file-sharing
+- file-upload-server
+- ftp-server
+- nas-frontend
+- tftp-server
+- webdav-server
+ReleaseNotes: |-
+  the FTP-server (default-disabled) would allow uploading to any folder that the copyparty process had permission to write to, but with certain limitations; see GHSA-phv8-wgjp-g4p9
+  recent important news
+  - v1.20.19 (2026-07-27) fixed an FTP-server vuln (upload outside defined volumes)
+  - v1.20.17 (2026-07-06) fixed a vuln when a volume has both filekeys and dirkeys enabled
+  - v1.20.17 (2026-07-06) introduced csp nonces, possibly breaking some javascript-based plugins
+  🧪 new features
+  - #1495 wopi integration -- edit office documents in the web-ui (thx @brandon-doornbos!) d57bb0c7 10db4236
+    - currently only works with collabora online as wopi client #1574 and there's no docs/examples #1575
+  - thumbnails: use embedded cover-image in videos when available 59524018
+  - thumbnails: folder-thumbs can be disabled with th-covers: no (volflag or global) 856fada3
+  - #1555 macos: add --srch-nfkc to fix searching for filenames / paths in CJK languages a7c99094
+    - reduces search performance to around 30% when enabled
+  - hooks: xbr / xar did not include old/new abspath as parameters; now they do c122e103
+  🩹 bugfixes
+  - ftp: fix GHSA-phv8-wgjp-g4p9 b331bb1c
+  - #1563 moving files between volumes could fail depending on OS and underlying filesystem c70dc7ac
+  - fix drag-drop uploading in certain glitchy KDE environments (thx @tilse!) daf144af
+  - hooks: xiu crashed if the fork-flag was set (thx @stackxp!) aa862353
+  - hooks: xau without json-flag would be given the wark (file hash) instead of the abspath bae77b90
+  - shares: fix markdown-viewer (?v) inside shares 6a9437b7
+  - ftp: fix logging from xbu hooks 9912a951
+  - fix slow boot if a volume had lots of files in its toplevel folder cdb474c8
+  - python2.7: fix multithreaded file-hashing 0f2040c3
+  🔧 other changes
+  - #1556 the libvips thumbnailer was demoted to last-fallback due to frequently using excessive amounts of ram ed0be42a
+  - if -lo points to an existing file, it will now be appended to instead of overwritten depending on --rlo b6abc33f
+  - #1530 nixos: the nix package now uses ffmpeg-headless instead of ffmpeg-full (thx @nyakase!) fface524
+  - slightly longer session cookie (was 20, now 24 chars) 537a99df
+  - Windows-specific:
+    - add a warning regarding the risks of DLL-hijacking when relevant bb40804f
+    - fix some trivial PATH-related footguns cea97ac6
+    - faster creation of sparse files bc45299b
+    - fix detection of filesystem characteristics 6226858b
+ReleaseNotesUrl: https://github.com/9001/copyparty/releases/tag/v1.20.19
+ManifestType: defaultLocale
+ManifestVersion: 1.12.0
diff --git a/...rmin/Express/7.29.0.0/Garmin.Express.yaml → ...001/copyparty/1.20.19/9001.copyparty.yaml b/...rmin/Express/7.29.0.0/Garmin.Express.yaml → ...001/copyparty/1.20.19/9001.copyparty.yaml
@@ -1,8 +1,8 @@
-# Automatically updated by the winget bot at 2026/Jun/11
-# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.12.0.schema.json
-
-PackageIdentifier: Garmin.Express
-PackageVersion: 7.29.0.0
-DefaultLocale: en-US
-ManifestType: version
-ManifestVersion: 1.12.0
+# Created with YamlCreate.ps1 Dumplings Mod
+# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.12.0.schema.json
+
+PackageIdentifier: 9001.copyparty
+PackageVersion: 1.20.19
+DefaultLocale: en-US
+ManifestType: version
+ManifestVersion: 1.12.0
diff --git a/...AceBIT/PasswordDepot/19/Corporate/19.2.2/AceBIT.PasswordDepot.19.Corporate.installer.yaml b/...AceBIT/PasswordDepot/19/Corporate/19.2.2/AceBIT.PasswordDepot.19.Corporate.installer.yaml
@@ -0,0 +1,20 @@
+# Automatically updated by the winget bot at 2026/Jul/27
+# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.12.0.schema.json
+
+PackageIdentifier: AceBIT.PasswordDepot.19.Corporate
+PackageVersion: 19.2.2
+InstallerType: inno
+Scope: machine
+FileExtensions:
+- pswd
+- pswe
+- pswx
+- pwde
+- pwdz
+ProductCode: '{E1531AF4-D6F3-49CC-8117-67E3B46E8304}_is1'
+Installers:
+- Architecture: x64
+  InstallerUrl: https://www.password-depot.de/download/v19/pdepot19CE.exe
+  InstallerSha256: 10BA58D4D82E1282BDD43FDEC202E1A62A3CC3124DD36F2BA0EBA3ADA174848F
+ManifestType: installer
+ManifestVersion: 1.12.0