Closed filips123 closed 1 year ago
Fixed with the introduction of scope override syntax in PR #367
In the upcoming release of winget-create, you would be able to execute the following command to fulfill your requirement
wingetcreate.exe update -s filips.FirefoxPWA -u "$INSTALLER_64BIT|x64|machine" "$INSTALLER_32BIT|x86|machine" "$INSTALLER_64BIT|x64|user" "$INSTALLER_32BIT|x86|user" -v $VERSION -t TEST
@filips123 This should be resolved in WinGet-Create 1.2.6.0 (although I understand your use case is no longer valid as the scopes were removed from the package)
Yeah, I'll close this issue.
Brief description of your issue
I have a package that is automatically updated using
wingetcreate update
from GitHub Actions. This worked fine, however, recently, the package manifest got updated to allow both per-user and per-machine installs (microsoft/winget-pkgs#103854). Because my installers support both scopes, this was done by duplicating an entry for each installer (there are two installers, one for 32-bit and one for 64-bit) and specifying each install scope once. So, there are now four installer entries with two different URLs.This means that apparently the package cannot be updated with
wingetcreate update
anymore...Steps to reproduce
First try, an existing command that was used for all previous versions:
So, I tried to specify all four URLs in the same order as they are specified in the manifest:
Expected behavior
wingetcreate update
should upload all installers and create an updated manifest.Actual behavior
wingetcreate update
does not upload installers and create a manifest.When only passing two (different) installer URLs (first command):
When passing all four installers URLs (second command):
Environment