New package: ByteForge.FIGPrint version 1.1.13#355356
New package: ByteForge.FIGPrint version 1.1.13#355356PaulStSmith wants to merge 3 commits intomicrosoft:masterfrom
Conversation
|
Validation Pipeline Run WinGetSvc-Validation-136-355356-20260404-1 |
There was a problem hiding this comment.
Pull request overview
Adds a new WinGet manifest set for ByteForge.FIGPrint v1.1.13, enabling installation via Windows Package Manager using the upstream GitHub release assets.
Changes:
- Added the version manifest (
ManifestType: version) for ByteForge.FIGPrint 1.1.13. - Added the default locale metadata (
ManifestType: defaultLocale) for en-US. - Added the installer manifest (
ManifestType: installer) using ZIP archives with a nested portable executable and command alias.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| manifests/b/ByteForge/FIGPrint/1.1.13/ByteForge.FIGPrint.yaml | Introduces the version manifest referencing default locale en-US for v1.1.13. |
| manifests/b/ByteForge/FIGPrint/1.1.13/ByteForge.FIGPrint.locale.en-US.yaml | Provides publisher/package metadata and short description for the default locale. |
| manifests/b/ByteForge/FIGPrint/1.1.13/ByteForge.FIGPrint.installer.yaml | Defines x64 and arm64 ZIP installers with a nested portable FIGPrint.exe and figprint alias. |
|
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.13.
Microsoft Reviewers: Open in CodeFlow