Skip to main content

Maintaining Etcher

This document is meant to serve as a guide for maintainers to perform common tasks.


Release Types

  • draft: A continues snapshot of current master, made by the CI services
  • pre-release (default): A continues snapshot of current master, made by the CI services
  • release: Full releases

Draft release is created from each PR, tagged with the branch name. All merged PR will generate a new tag/version as a pre-release. Mark the pre-release as final when it is necessary, then distribute the packages in alternative channels as necessary.



  • Test the prepared release and build artifacts properly on all supported operating systems to prevent regressions that went uncaught by the CI tests (see
  • If regressions or other issues arise, create issues on the repository for each one, and decide whether to fix them in this release (meaning repeating the process up until this point), or to follow up with a patch release


Generating binaries


Make sure to set the analytics tokens when generating production release binaries:



Clean dist folder

NOTE: Make sure to adjust the path as necessary (here the Etcher repository has been cloned to /home/$USER/code/etcher)

Generating artifacts

The artifacts are generated by the CI and published as draft-release or pre-release. electron-builder is used to create the packaged application.

Mac OS

ATTENTION: For production releases you'll need the code-signing key, and set CSC_NAME to generate signed binaries on Mac OS.


ATTENTION: For production releases you'll need the code-signing key, and set CSC_LINK, and CSC_KEY_PASSWORD to generate signed binaries on Windows.


  • Keep in mind to also generate artifacts for x86, with TARGET_ARCH=x86.

Uploading packages to Cloudfront

Log in to cloudfront and upload the rpm and deb files.

Dealing with a Problematic Release

There can be times where a release is accidentally plagued with bugs. If you released a new version and notice the error rates are higher than normal, then revert the problematic release as soon as possible, until the bugs are fixed.

You can revert a version by deleting its builds from the S3 bucket and Bintray. Refer to the Makefile for the up to date information about the S3 bucket where we push builds to, and get in touch with the operations team to get write access to it.

The Etcher update notifier dialog and the website only show the a certain version if all the expected files have been uploaded to it, so deleting a single package or two is enough to bring down the whole version.

Use the following command to delete files from S3:

aws s3api delete-object --bucket <bucket name> --key <file name>

The Bintray dashboard provides an easy way to delete a version's files.

Submitting binaries to Symantec

  • Report a Suspected Erroneous Detection
  • Fill out form:
    • Select Submission Type: "Provide a direct download URL"
    • Name of the software being detected: Etcher
    • Name of detection given by Symantec product: WS.Reputation.1
    • Contact name: Ltd
    • E-mail address: [email protected]
    • Are you the creator or distributor of the software in question? Yes