Arduino Pro IDE

Download

You can download the latest version of the Arduino Pro IDE application for the supported platforms from the GitHub release page or following the links in the following table.

Latest version

Platform	32 bit	64 bit
Linux		Linux 64 bit
Linux ARM	🚧 Work in progress...	🚧 Work in progress...
Windows		Windows 64 bit
macOS		macOS 64 bit

Previous versions

These are available from the GitHub releases page.

Nightly builds

These builds are generated every day at 03:00 GMT from the master branch and should be considered unstable. In order to get the latest nightly build available for the supported platform, use the following links:

Platform	32 bit	64 bit
Linux		Nightly Linux 64 bit
Linux ARM	🚧 Work in progress...	🚧 Work in progress...
Windows		Nightly Windows 64 bit
macOS		Nightly macOS 64 bit

These links return an HTTP 302: Found response, redirecting to latest generated builds by replacing latest with the latest available build date, using the format YYYYMMDD (i.e for 2019/Aug/06 latest is replaced with 20190806 )

Build from source

If you’re familiar with TypeScript, the Theia IDE, and if you want to contribute to the project, you should be able to build the Arduino Pro IDE locally. Please refer to the Theia IDE prerequisites documentation for the setup instructions.

Build

yarn

Rebuild the native dependencies

yarn rebuild:electron

Note: this step takes long. It completes in 4-5 minutes on a MacBook Pro, 2.9 GHz Quad-Core Intel Core i7.

Start

yarn start

CI

This project is built on GitHub Actions.

• Snapshot builds run when changes are pushed to the master branch, or when a PR is created against the master branch. For the sake of the review and verification process, the build artifacts can be downloaded from the GitHub Actions page. Note: due to a limitation with the GH Actions UI, you cannot download a particular build, but you have to get all together inside the build-artifacts.zip.
• Nightly builds run every day at 03:00 GMT from the master branch.
• Release builds run when a new tag is pushed to the remote. The tag must follow the semver. For instance, 1.2.3 is a correct tag, but v2.3.4 won't work. Steps to trigger a new release build:
  • Create a local tag:

  git tag -a 1.2.3 -m "Creating a new tag for the `1.2.3` release."
  

  • Push it to the remote:

   git push origin 1.2.3