Add WinGet installation instructions for Arduino CLI

[tanakamasayuki]

Added installation instructions for Arduino CLI using WinGet on Windows.

Please check if the PR fulfills these requirements

See how to contribute

• The PR has no duplicates (please search among the Pull Requests
  before creating one)
• The PR follows
  our contributing guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• UPGRADING.md has been updated with a migration guide (for breaking changes)
• configuration.schema.json updated if new parameters are added.

What kind of change does this PR introduce?

docs update.

Other information

arduino-cli version
winget install ArduinoSA.CLI
arduino-cli version

I tested the above command on Windows 11.
In PowerShell, the path will not be reflected unless you start a new shell.

[CLAassistant]

All committers have signed the CLA.

[per1234]

Thanks for taking the time to submit a pull request @tanakamasayuki.

We only list the installation methods that are officially maintained by the Arduino company. The Windows Package Manager package was created by a 3rd party without any involvement from us.

Because we do not maintain the package, we can not guarantee that it will be up to date. It is entirely up to the community to add new versions, and it is common for the community to not manage to keep packages up to date. And in fact this is exactly what has already happened. The latest version available from the Windows Package Manager is 1.2.2. We have made two additional releases which contain important enhancements and fixes since that time. So the use of winget to install Arduino CLI is actually harmful at this time.

For this reason, we are not able to accept your proposal for addition of this installation option to the official documentation.

[jo-chemla]

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 a github 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.

Uses winget-releaser Requires a Classic Github Personal Access Token with public_repo scope is created, following this link, then the Token can be added to the repo as a secret named WINGET_ACC_TOKEN. See below, that user also will have to fork the winget-pkgs repository.

Notes:
You will need to create a classic Personal Access Token (PAT) with public_repo scope. New fine-grained PATs aren't supported by the action. Review #172 for information.
Fork microsoft/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 WinGet
on:
  release:
    types: [ released ]
jobs:
  publish:
    runs-on: windows-latest
    steps:
      - uses: vedantmgoyal9/winget-releaser@main
        with:
          identifier: ArduinoSA.CLI
          token: ${{ secrets.WINGET_TOKEN }}
          installers-regex: '\.exe$'

[jo-chemla]

Hi @per1234 would you be interested in the above automated github action workflow being pushed as a PR to arduino/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!

[per1234]

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.

[jo-chemla]

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