Fix Winget package identifier #156
Conversation
Package is still stored in microsoft/winget-pkgs as ViGEm.HidHide. A new package could be submitted and users of the previous package migrated if the package identifier change is still needed; providing the updated version to users first.
|
Why did you change the identifier to the one that's deprecated, I don't understand the point of this change, please elaborate. |
|
https://github.com/nefarius/HidHide/actions/runs/9617849637/job/26530498455 The issue is that |
|
Well that's too bad then, I will not use that name anymore for reasons I explained quite thoroughly. Is there no "deprecate package X, replace with package Y" concept in winget? I am not really a fan of getting involved with these package managers myself, I barely have the time for maintenance without these extra distractions. |
|
related: microsoft/winget-cli#4344 But understandable. I'll see if I can make the PR creating the new package identifier. |
Package is still stored in microsoft/winget-pkgs as ViGEm.HidHide. A new package could be submitted and users of the previous package migrated if the package identifier change is still needed; providing the updated version to users first.
The updated workflow shouldn't be executed for this release, as a fixed manifest has already been PR'd, see linked.
Related:
#155
microsoft/winget-pkgs#160057
microsoft/winget-pkgs#160054