Kaleb Luedtke
Kaleb Luedtke
> > @ stephengillie - Can you try the PR that I raised into your fork? > > I'm not sure how to do this. I don't see a PR...
[Policy] Unblocked; Will require `ManifestVersion: 1.9.0` with `ArchiveBinariesDependOnPath: true`
* Related to https://github.com/microsoft/winget-create/discussions/160
@Gijsreyn - instead of a validate set, why not use a validate script? Something like - ``` [ValidateScript({ if ($_ -notin (Get-TimeZone -ListAvailable).Id) { throw "$_ is not a TimeZone...
Ah, so this is really more related to * https://github.com/microsoft/winget-create/issues/380 I assumed it was an issue with wingetcreate because the header said the manifests were created with wingetcreate
I'm pretty sure this is intended behavior based on the error message shown. If there are multiple EXE's inside the zip file, selecting the correct one for the update could...
I wonder if there isn't a need for an object type input something like: ```json [ { "URL:": "https://example.com/1.exe", "Scope": "user", "Architecture": "x64", "DisplayVersion": "1.2.3_64" }, { "URL:": "https://example.com/2.exe", "Scope":...
I could also see an AI assisting with metadata completion / translation for when a Locale manifest is missing data present in the DefaultLocale manifest. Or possibly suggesting to backfill...
This is actually correct behavior due to how version Parsing works in WinGet. WinGet splits the version into parts by the periods, and compares each part one at a time...
My mistake - meant to apply this to the PR