This is a small guide to package and publish Etcher to all supported operating systems.
Etcher supports production and snapshot release types. Each is
published to a different S3 bucket, and production release types are code
signed, while snapshot release types aren't and include a short git commit-hash
as a build number. For example,
1.0.0-beta.19 is a production release type,
1.0.0-beta.19+531ab82 is a snapshot release type.
In terms of comparison:
1.0.0-beta.19 (production) <
1.0.0-rc.1 (production) <
1.0.0-rc.1+7fde24a (snapshot) <
1.0.0 (production) <
1.0.0+2201e5f (snapshot). Keep in mind that if you're
running a production release type, you'll only be prompted to update to
production release types, and if you're running a snapshot release type, you'll
only be prompted to update to other snapshot release types.
The build system creates (and publishes) snapshot release types by default, but
you can build a specific release type by setting the
variable. For example:
make <target> RELEASE_TYPE=snapshot make <target> RELEASE_TYPE=production
We can control the version range a specific Etcher version will consider when
showing the update notification dialog by tweaking the
Etcher has a setting to include the unstable update channel. If this option is
set, Etcher will consider both stable and unstable versions when showing the
update notifier dialog. Unstable versions are the ones that contain a
pre-release tag. For example:
- Production unstable version:
- Snapshot unstable version:
- Production stable version:
- Snapshot stable version:
Get our Apple Developer ID certificate for signing applications distributed outside the Mac App Store from the balena.io Apple account.
Install the Developer ID certificate to your Mac's Keychain by double clicking on the certificate file.
The application will be signed automatically using this certificate when packaging for OS X.
Get access to our code signing certificate and decryption key as a balena.io employee by asking for it from the relevant people.
Place the certificate in the root of the Etcher repository naming it
The resulting installers will be saved to
Run the following commands:
make electron-installer-dmg make electron-installer-app-zip
make electron-installer-appimage make electron-installer-debian
make electron-installer-zip make electron-installer-nsis
Publishing to Bintray
We publish GNU/Linux Debian packages to Bintray.
Make sure you set the following environment variables:
Run the following command:
Publishing to S3
Make sure you have the AWS CLI tool installed and configured to access balena.io's production or snapshot S3 bucket.
Run the following command to publish all files for the current combination of platform and arch (building them if necessary):
Publishing to Homebrew Cask
Casks/etcher.rbwith the new version and
Send a PR with the changes above to
Post messages to the Etcher forum announcing the new version of Etcher, and including the relevant section of the Changelog.