Replies: 2 comments 2 replies
-
|
I had the thought about the workflow at the end of writing that, submitted it, then went and looked and there's already a winget workflow. It seems that the package ID needs to be updated. I'll PR that |
Beta Was this translation helpful? Give feedback.
-
|
Never mind, it was changed because ViGEm is trademarked? But it's still what the package is stored under, and the new package hasn't been created. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
On one hand it's good to document things? On the other hand this was kinda pointless as I finished investigating and submitted a potential fix without needing input. Ah well. |
Beta Was this translation helpful? Give feedback.
-
New user of HidHide (at least I wasn't aware I was using it with DS4Windows before this week); I'm trying to standardise my Windows installs using Winget, and was surprised to see that there's been a newer version since 1.5.212 available here since May. It seems that creating an issue such as microsoft/winget-pkgs#160054 is required to kick off the process of bots talking to bots to get the new version submitted to the package repository. This could perhaps be added to an Actions workflow?
Beta Was this translation helpful? Give feedback.
All reactions