[pull] master from microsoft:master

.github/PULL_REQUEST_TEMPLATE.md

@@ -9,7 +9,7 @@ Manifests
 - [ ] This PR only modifies one (1) manifest
 - [ ] Have you [validated](https://github.com/microsoft/winget-pkgs/blob/master/doc/Authoring.md#validation) your manifest locally with `winget validate --manifest <path>`?
 - [ ] Have you tested your manifest locally with `winget install --manifest <path>`?
-- [ ] Does your manifest conform to the [1.10 schema](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.10.0)?
+- [ ] Does your manifest conform to the [1.12 schema](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.12.0)?
 
 Note: `<path>` is the directory's name containing the manifest you're submitting.
 

.github/instructions/manifests.instructions.md

@@ -6,13 +6,13 @@
 
 ## Repository Overview
 
 This is the **Windows Package Manager (WinGet)** community repository containing **~415,000+ manifest files** for software packages installable via `winget`. The repository is a **manifest-only** repository - no application code, just YAML metadata files describing how to install Windows applications.
 
 **Key Facts:**
 - **Primary Language:** YAML manifest files, PowerShell scripts for tooling
 - **Target Runtime:** Windows 10/11, Windows Package Manager client
 - **Size:** Large repository with alphabetically organized manifests
-- **Schema:** Uses multi-file YAML manifests (version 1.10.0 recommended, 1.9.0 also supported)
+- **Schema:** Uses multi-file YAML manifests (version 1.12.0 recommended, 1.10.0 also supported)
 - **Supported Installers:** MSIX, MSI, APPX, EXE only (scripts are not supported)
 
 ## Critical: How This Repository Works
@@ -88,7 +88,7 @@
 
   For:
   ```
   manifests/m/Microsoft/WSL/2.6.2/
   ```
   Only search within:
   ```
@@ -111,7 +111,7 @@
 
 ## Summary
 
 - Only analyze **diffs** and **local package manifests**.
 - Never run expensive global scans.
 - Never crawl the entire `manifests/` directory.
 - Keep all search operations **package-scoped** for reliability.

.github/policies/labelAdded.manifestValidationError.yml

@@ -24,7 +24,7 @@ configuration:
                 Hello ${issueAuthor},
 
 
-                Please verify the manifest file is compliant with the package manager [1.10.0 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.10.0).
+                Please verify the manifest file is compliant with the package manager [1.12.0 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.12.0).
 
 
                 Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.

.github/policies/labelAdded.manifestVersionError.yml

@@ -24,7 +24,7 @@ configuration:
                 Hello ${issueAuthor},
 
 
-                The package manager bot determined that the ManifestVersion key does not match any version currently approved for release. Please verify the manifest file is compliant with the package manager [1.10.0 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.10.0).
+                The package manager bot determined that the ManifestVersion key does not match any version currently approved for release. Please verify the manifest file is compliant with the package manager [1.12.0 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.12.0).
 
 
                 For details on the specific error, see the details link below in the build pipeline.

.github/policies/labelAdded.zipBinary.yml

@@ -28,7 +28,7 @@ configuration:
                 * microsoft/winget-cli/issues/2711
 
 
-                To ensure this package works correctly for all users, the property `ArchiveBinariesDependOnPath` must be set to `true` at either the installer level or root level in the installer manifest. Additionally, your manifest will need to conform to the [1.10.0 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.10.0). Please update your PR accordingly.
+                To ensure this package works correctly for all users, the property `ArchiveBinariesDependOnPath` must be set to `true` at either the installer level or root level in the installer manifest. Additionally, your manifest will need to conform to the [1.12.0 manifest specification](https://github.com/microsoft/winget-pkgs/tree/master/doc/manifest/schema/1.12.0). Please update your PR accordingly.
 
 
                 Template: msftbot/blockingIssue/zipBinary

README.md

@@ -10,7 +10,7 @@
 This repository contains the manifest files for the **Windows Package Manager** default source. You are highly encouraged to submit manifests for your favorite application.
 
 > [!IMPORTANT]
-> At this time installers must be MSIX, MSI, APPX, MSIXBundle, APPXBundle, or .exe application installers. Script-based installers and fonts are not currently supported.
+> At this time installers must be MSIX, MSI, APPX, MSIXBundle, APPXBundle, or .exe application installers. Font files (.ttf, .ttc, .otf, .otc, and .fnt) are also supported. Script-based installers are not currently supported.
 
 The **Windows Package Manager** is an [open source client](https://github.com/microsoft/winget-cli) designed for command-line usage. If you are interested in exploring private repositories offering private WinGet package hosting, see [private repositories](doc/private/README.md).
 

doc/Authoring.md

@@ -1,7 +1,7 @@
-[Manifest Specification]:   manifest/schema/1.10.0
-[versionSchema]:            manifest/schema/1.10.0/version.md
-[defaultLocaleSchema]:      manifest/schema/1.10.0/defaultLocale.md
-[installerSchema]:          manifest/schema/1.10.0/installer.md
+[Manifest Specification]:   manifest/schema/1.12.0
+[versionSchema]:            manifest/schema/1.12.0/version.md
+[defaultLocaleSchema]:      manifest/schema/1.12.0/defaultLocale.md
+[installerSchema]:          manifest/schema/1.12.0/installer.md
 
 # Authoring Manifests
 

doc/Policies.md

@@ -10,6 +10,7 @@ WinGet supports the following installer types:
 - **MSIX**
 - **MSI**
 - **Exe-based installers**
+- **Font files**
 
 These installer types may also be nested within the `.zip` (compressed) installer type.
 **Scripts are expressly disallowed as installers.** Examples include:
@@ -39,3 +40,8 @@ WinGet supports a singleton manifest type, but it is prohibited in the community
 
 ## Manifest URLs
 The URLs in manifests should come from official sources/publishers for packages. In particular any URLs for installers need to be discoverable on the publishers website. In many cases the URLs for installers come from a CDN, and HTTP redirects are used to find the "final" url for installers. Some software is delivered via a "vanity" URL and publishers replace the binaries which will cause a hash mismatch until a new version of the manifest is published. The preference for WinGet manifests is to use unique URLs per version of a package to avoid the hash-mismatch errors.
+
+## Manifest Root Policy
+This repository has two manifest root folders, `manifests` and `fonts` with InstallerType policy enforcement as follows:
+- `manifests` - InstallerType and NestedInstallerType `font` is not allowed.
+- `fonts` - InstallerType `font` and `zip` are the only permitted InstallerTypes, and `font` is the only permitted NestedInstallerType.

doc/manifest/schema/1.12.0/README.md

@@ -0,0 +1,69 @@
+[schemaFolder]:                             https://github.com/microsoft/winget-cli/tree/master/schemas/JSON/manifests/v1.12.0
+[versionSchema]:                            https://github.com/microsoft/winget-cli/tree/master/schemas/JSON/manifests/v1.12.0/manifest.version.1.12.0.json
+[defaultLocaleSchema]:                      https://github.com/microsoft/winget-cli/tree/master/schemas/JSON/manifests/v1.12.0/manifest.defaultLocale.1.12.0.json
+[localeSchema]:                             https://github.com/microsoft/winget-cli/tree/master/schemas/JSON/manifests/v1.12.0/manifest.locale.1.12.0.json
+[installerSchema]:                          https://github.com/microsoft/winget-cli/tree/master/schemas/JSON/manifests/v1.12.0/manifest.installer.1.12.0.json
+[Windows Package Manager Manifest Creator]: https://github.com/microsoft/winget-create
+[YAML Create]:                              https://github.com/microsoft/winget-pkgs/blob/master/Tools/YamlCreate.ps1
+
+# Windows Package Manager
+
+## Manifest Schema 1.12
+
+The Windows Package Manager 1.12 client does not support all fields in the 1.12 schema.
+
+The Windows Package Manager uses manifests (YAML files) to locate and install packages for Windows users. This specification provides references to JSON schemas as well as best practices.
+
+Manifests submitted to the Windows Package Manager Community Repository should be submitted as a multi-file manifest. Only one version of a package may be submitted per pull request. The [singleton](singleton.md) manifest format is supported by the client, but has been deprecated in the community repository. Rich tooling exists to generate manifests. The [Windows Package Manager Manifest Creator] and [YAML Create] were both designed to produce well formed and rich manifests.
+
+A multi-file manifest contains:
+* One [version](version.md) ([JSON Schema][versionSchema]) file
+* One [default locale](defaultLocale.md) ([JSON Schema][defaultLocaleSchema]) file
+* One [installer](installer.md) ([JSON Schema][installerSchema]) file
+* Additional optional [locale](locale.md) ([JSON Schema][localeSchema]) files
+
+## YAML file name and folder structure
+YAML files shall be added to the repository with the following folder structure:
+manifests / p / publisher / package / packageVersion / publisher.package.<manifestFile>.yaml
+
+Example:
+`manifests/m/Microsoft/WindowsTerminal/1.9.1942/Microsoft.WindowsTerminal.installer.yaml`
+
+* Manifests are partitioned by the first letter of the publisher name (in lower case). For example: m.
+* Publisher folder is the name of the company that publishes the tool. For example: Microsoft.
+* The child folder package is the name of the application or tool. For example: WindowsTerminal.
+* The child folder package version is the version of the package. For example: 1.6.10571.0.
+* The filename must be a combination of the publisher name and the application name. For example: Microsoft.WindowsTerminal.yaml.
+
+The publisher and application folders MUST match the values used to define the Id. See PackageIdentifier: in the YAML for more detail.
+The version in the folder name MUST match the version field value in the YAML file. See PackageVersion: in the YAML for more detail.
+
+There are two primary types of manifests. A single file manifest (singleton) and a multi-file manifest.
+[JSON schemas][schemaFolder] have been provided
+to help strongly type attributes and requirements.
+
+## YAML Syntax
+Each field in the file must be PascalCased and cannot be duplicated.
+
+## Best Practices
+The package identifier must be unique. You cannot have multiple submissions with the same package identifier. Only one pull request per package version is allowed.
+
+Avoid creating multiple publisher folders. For example, do not create "Contoso Ltd." if there is already a "Contoso" folder.
+
+All tools must support a silent install to be permitted in the Windows Package Manager Community Repository. If you have an executable that does not support a silent install, then we cannot provide that tool at this time.
+
+Provide as many fields as possible. The more meta-data you provide the better the user experience will be. In some cases, the fields may not yet be supported by the Windows Package Manager client (winget.exe).
+
+The length of strings in this specification should be limited to 100 characters before a line break.
+
+## Summary of Changes from 1.10.0
+
+### [Version](version.md)
+* No Changes
+### [Default Locale](defaultLocale.md)
+* No Changes
+### [Installer](installer.md)
+* Added `font` to InstallerType
+* Added `font` to NestedInstallerType
+### [Locale](locale.md)
+* No Changes