New package: ByteForge.FIGPrint version 1.1.12#355346
New package: ByteForge.FIGPrint version 1.1.12#355346PaulStSmith wants to merge 6 commits intomicrosoft:masterfrom
Conversation
|
Validation Pipeline Run WinGetSvc-Validation-136-355346-20260404-1 |
There was a problem hiding this comment.
Pull request overview
Adds a new WinGet package manifest set for ByteForge.FIGPrint version 1.1.12, enabling installation of the FIGPrint CLI via Windows Package Manager.
Changes:
- Added the version manifest for ByteForge.FIGPrint 1.1.12.
- Added the defaultLocale (en-US) metadata manifest.
- Added the installer manifest with x64 and arm64 ZIP-based portable installers.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| manifests/b/ByteForge/FIGPrint/1.1.12/ByteForge.FIGPrint.yaml | Introduces the version manifest pointing to the en-US default locale. |
| manifests/b/ByteForge/FIGPrint/1.1.12/ByteForge.FIGPrint.locale.en-US.yaml | Adds publisher/package metadata and license info for the default locale. |
| manifests/b/ByteForge/FIGPrint/1.1.12/ByteForge.FIGPrint.installer.yaml | Defines x64/arm64 installers as ZIP archives with a portable nested EXE and alias. |
manifests/b/ByteForge/FIGPrint/1.1.12/ByteForge.FIGPrint.locale.en-US.yaml
Outdated
Show resolved
Hide resolved
manifests/b/ByteForge/FIGPrint/1.1.12/ByteForge.FIGPrint.installer.yaml
Outdated
Show resolved
Hide resolved
|
@microsoft-github-policy-service agree [company="ByteForge"] |
|
Validation Pipeline Run WinGetSvc-Validation-136-355346-20260404-2 |
|
@microsoft-github-policy-service agree |
|
Validation Pipeline Run WinGetSvc-Validation-136-355346-20260404-3 |
|
Validation Pipeline Run WinGetSvc-Validation-136-355346-20260404-4 |
|
Hello @PaulStSmith, Please verify the manifest file is compliant with the package manager 1.12.0 manifest specification. Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct. You can also validate your manifest using the For details on the specific error, see the details link below in the build pipeline. Template: msftbot/validationError/manifest/content |
Automated submission from ByteForge.FIGPrint v1.1.12.
Microsoft Reviewers: Open in CodeFlow