Repository navigation
docs: adding possibility to install from winget - #829
Conversation
docs: adding possibility to install from winget
|
This is great. Do you know who set it up? I'm trying to understand if every newly published version will show up. |
|
@SeanFeldman thanks! |
|
I added publishing to WinGet in #795, but it didn't handle prelease releases so it failed. Until that works we cannot be sure that the package is genuine even if we verify the current version. Therefore we should have a similar text as we have for the Scoop installation. I suggest the following text is added:
There has been some breaking changes to the code so the next version should be a major version change. I want to have the ability to set filter per namespace, #706, as part of the next release so I haven't made a new release. Hopefullly, WinGet publishing will work in that release. |
|
I took another look at the main branch and the only major change is the increase in .NET Framework version. I consider that just a minor version upgrade so I will try to create a successful release including having it published to WinGet. The logs from the failed publishing to WinGet are not available anymore so I have to start with failing that again 😺. |
|
WinGet now supports zip deployment, which we already produce. Hopefully that should help. |
|
I created WinGet release 6.1.0 manually. Today Defender on my computer reports that 6.1.0 contains a threat. Yesterday it was fine. However after extracting all files and scanning them everything is fine. |

Closes #455
This pull request updates the
README.mdfile to include instructions for installing the Service Bus Explorer using Winget, providing an additional installation option for users.Documentation Updates:
README.md: Added a new section titled "Using Winget" with installation instructions for Service Bus Explorer via the Winget package manager.