All committers have signed the CLA.

Sorry to revive a recently closed PR.

@per1234 Would the Arduino team be interested in having a github action workflow based on winget-releaser (based on Komac) to push every new Arduino CLI github-release to the winget package registry? It is the official windows package manager, comes pre-installed with every windows >= 11 fresh install, does make a lot of sense.

Note, in the meantime, I've created a cron running every night via agithub action that pushes new arduino CLI releases to winget registry as soon as they are detected, so the discrepancy should be removed. Note it would still be preferable to have the core arduino team officially support publishing the package, especially given how straightforward it is with the below github action.

Useswinget-releaser Requires aClassic Github Personal Access Token withpublic_repo scope is created, followingthis link, then the Token can be added to the repo as a secret namedWINGET_ACC_TOKEN. See below, that user also will have to fork the winget-pkgs repository.

Notes:
You will need to create aclassic Personal Access Token (PAT) withpublic_repo scope. New fine-grained PATs aren't supported by the action. Review#172 for information.
Forkmicrosoft/winget-pkgs under the same account/organization as the project's repository. If you are forking winget-pkgs on a different account (e.g. bot/personal account), you can use the fork-user input to specify the username of the account where the fork is present.

name:Publish to WinGeton:release:types:[ released ]jobs:publish:runs-on:windows-lateststeps:      -uses:vedantmgoyal9/winget-releaser@mainwith:identifier:ArduinoSA.CLItoken:${{ secrets.WINGET_TOKEN }}installers-regex:'\.exe$'

Hi@per1234 would you be interested in the above automated github action workflow being pushed as a PR toarduino/arduino-cli? Would mean every new github release ends up up-to-date in winget-pkgs official microsoft repository, no more out-of-date via automated workflow!

Hi@jo-chemla. I mostly only serve a janitorial role for this project. The decision regarding your proposal would need to be made by someone with more of a management role.

In order to ensure those team members will notice and be able to effectively track your proposal (which they might not do here in this closed issue), I recommend you create a dedicated issue. If you find it more convenient to make the proposal in the form of a pull request adding the workflow instead of an issue, that is perfectly fine too.

Thanks for getting back, just did submit the PR here!#3033