[Feature]: add it to winget repository

[ZiedYousfi]

Before submitting

• I searched existing issues and did not find a duplicate.
• I am describing a concrete problem or use case, not just a vague idea.

Area

Build, CI, or release tooling

Problem or use case

This is mostly to know if you would accept adding it to the Winget repository so that it's easier to manage the versions of the desktop app.

Proposed solution

I will do the PR to the winget repository if you accept.

Why this matters

Because of the fast releases of updates and not wanting to have to manually update it on our system and not having to use npm to manage the versions it will be easier to have it to packages repositories

Smallest useful scope

Honestly just giving a policy if it's ready to be added to packages repos and what the identifiers should be.

Alternatives considered

No response

Risks or tradeoffs

No response

Examples or references

No response

Contribution

• I would be open to helping implement this.

[juliusmarminge]

Sure, why not.

Never done it, is it better if we publish it as an org part of our CI script or how does it work?

[ZiedYousfi]

For the first time when we add it to the repo we need a manual PR and then after that you can add it to the release CI because they made a CLI to update the package version

So i can do the first PR to the winget repo and if it gets added i can do the PR to the release ci in this repository. If you're okay with that could you tell me what is the org name I should put for the publishing of it

[juliusmarminge]

The app is signed with Azure Trusted Signing with the org T3 Tools Inc

[ZiedYousfi]

Ok I will do it as soon as I get the time to. Thank you

[ZiedYousfi]

Okay it's done and because it's already signed it will be easy to manually upgrade it so there's no need to change CI thank you for your time