Arduino published arduino-cli v1.6.0 on GitHub on 2026-11-10. It follows v1.5.1, the previous release in the project's changelog. The headline item is Windows on ARM64. Most of the changelog, though, deals with the things that matter in continuous integration and IDE back ends: memory use, slow installs, files left broken by an interrupted install, and crashes under concurrent access. It is a release aimed at people whose builds call arduino-cli over and over.
Below we go through the changes in the order an integrator would care about them, citing the pull-request numbers from the release notes so you can check each one against your own setup.
Windows on ARM64: released, but not in the docs table yet
The release notes list "Arduino CLI is now available for Windows on ARM64" under Improvements (#3249). That is relevant to anyone running toolchains on Snapdragon-based Windows laptops or ARM64 Windows CI runners, who would otherwise be running an x64 build under emulation.
One caveat. When we checked the installation page on docs.arduino.cc, its download table listed Windows 32-bit and 64-bit zips, a 64-bit MSI, macOS 64-bit and ARM64 builds, and Linux variants. It had no Windows ARM64 entry. The project's own documentation site also lagged: its /latest/ path redirected to the 1.5 installation docs, so 1.6 documentation had not been published when we checked. Scripts that scrape the docs download table to choose an artifact will not find an ARM64 Windows build yet. The release page is the authoritative source for 1.6.0.
Installs that survive a power cut
The fix with the most practical impact is easy to miss in the list. Per the release notes, installed files are now safely written to disk, so a power loss during an installation no longer leaves broken files (#3329). A half-written core or tool left in the data directory is the kind of failure this targets. It is most relevant to machines that can lose power or be cut off mid-install, such as classroom machines, lab benches and single-board computers used as build hosts. Ephemeral CI runners that rebuild from scratch are less exposed; persistent self-hosted runners with cached data directories are the likelier beneficiaries.
A related change: pressing Ctrl-C twice now always stops the CLI (#3288). That is useful for interactive users and for wrapper tools that forward signals.
Speed and memory
The release lists three performance items:
- Lower memory use when loading the library index (#3261, #3343). The release notes give no figures. Memory-constrained hosts and containers with tight limits are the likely beneficiaries.
- Faster
uploadwhen no port is given and the board does not need one (#3348). - Faster installation of cores and tools packed as .xz archives (#3332). The notes give no benchmark. If your CI installs a platform on every run, this is the change to time before and after.
The notes publish no benchmark numbers for any of these, so we quote none. Measure them on your own workload.
Package index and download changes
Two improvements change how the CLI fetches packages:
- Package index URLs no longer need to end with a file name (#3227). Vendors and internal mirrors that serve a third-party board index from a bare path can likely use it directly.
- Downloads from GitHub use
GITHUB_TOKEN, if it is set, to avoid GitHub download limits (#3201). GitHub Actions jobs and other environments that already export a token may benefit. The flip side: check what scope that token has in your pipeline, because the CLI will now use it for GitHub downloads.
Crash and correctness fixes
The rest of the fixes are narrow but worth knowing about if any of them has bitten you:
- A crash when a board does not define its flash memory size is fixed (#3306).
- A crash when the configuration is read and changed at the same time is fixed (#3216). This is most likely to matter to IDEs and daemons that talk to a long-running CLI instance.
- Libraries whose
utilityfolder is a symlink now compile correctly (#3257). - Library detection no longer fails when the compiler prints coloured error messages (#3248).
- Platform versions that are installed but no longer in any package index are now shown correctly (#3233).
For tool and IDE developers
Two changes target people who build on the CLI rather than run it:
- The gRPC API now exposes the libraries that a platform provides (#3295). Front ends that use the daemon can query this directly.
- Tools can be force-installed for a different architecture (#3292). This looks useful for preparing toolchain bundles or offline images for another machine, though the notes do not describe use cases.
The release notes also credit five new contributors.
What It Means for Makers
Who it is for: mostly people who automate Arduino builds, meaning CI pipelines, classroom image builders and IDE or editor integrations on the gRPC daemon, plus anyone who wants to run the CLI natively on a Windows ARM64 machine. Someone who compiles a sketch now and then from the terminal will mainly notice faster .xz installs and safer installs. Little else changes for them.
What it replaces or enables: 1.6.0 follows v1.5.1. It makes native Windows ARM64 use possible, allows package index URLs without a file name, and lets GitHub downloads use an existing GITHUB_TOKEN. Before upgrading a pinned CI setup, integrators should check three things:
- Whether any script picks a download artifact from the docs table. That table did not list Windows ARM64 when we checked.
- Whether
GITHUB_TOKENis exported in jobs that run the CLI, and whether you want it used for downloads. - Whether any parsing of
liborcoreoutput, or of compiler output, depended on the old behaviour fixed in #3248 and #3233.
The installation documentation shows how to pin a specific version with the install script. Pinning is the safe way to roll out 1.6.0 deliberately rather than picking it up on the next unpinned run.
Price and availability: none of the sources we used states a price. v1.6.0 is a published stable release on the project's GitHub releases page, dated 2026-11-10. The 1.5 documentation lists Homebrew, the install script, pre-built binaries and building from source as install methods. 1.6-specific documentation had not been published when we checked.