networkException

Well I don't like that action pulling a powershell script from `main` even on tagged releases but in principle we'd use something like that yes

Yea we might just fork it. @Nifury do you want to take a look at that? I'd happily do it as well but as the author you have more experience...

> I think I'm going to submit a PR manually sounds good > Yeah we need a PAT to create a pull request in the winget repository. Oh I see....

why that? I think it would be better to just update the existing package

> Can we update an existing path? Don't we need a kind of key to authenticate in order to publish our release? I believe we only require approval from one...

Its the same binary with different install scopes

well those permissions can be adjusted i guess an actual maintainer account would also have its advantages

I guess we could add .1.1 or something It's not obvious to me how winget determines the latest version but as long as we don't break that mechanism adding more...

Sorry to hear that this broke your updates completely. I'm not really sure how to proceed here sadly

The debian packaging is effectively unmaintained. I fear we and the current maintainer are lacking the capacity to keep it updated. At the moment I would recommend using the flatpak