From c70508edb1fa600387fe1b0c0dedd56f264353e4 Mon Sep 17 00:00:00 2001 From: Cheng Zhao Date: Tue, 26 Sep 2017 10:30:42 +0900 Subject: [PATCH] docs: How to re-upload binaries manually --- docs/development/releasing.md | 30 ++++++++++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/docs/development/releasing.md b/docs/development/releasing.md index c30f1959c866..1f289382b617 100644 --- a/docs/development/releasing.md +++ b/docs/development/releasing.md @@ -231,3 +231,33 @@ Then edit the release on GitGub: 1. Remove `beta` from the release name: electron v1.7.5 ~~beta~~ 1. Uncheck the `prerelease` checkbox. 1. Click "Update release" + +## Fix missing binaries of a release manually + +In the case of a corrupted release with broken CI machines, we might have to +re-upload the binaries for a already published release. + +The first step is to go to the Releases page and delete the corrupted binaries +with the `SHASUMS256.txt` checksum file. + +Then manually create distributions for each platform and upload them: + +```sh +# Checkout the version to re-upload. +git checkout vTHE.RELEASE.VERSION + +# Do Release build. +./script/bootstrap.py --target_arch [arm|x64|ia32] +./script/build.py -c R +./script/create-dist.py + +# Explicitly allow overwritting a published release. +./script/upload.py --overwrite +``` + +After re-uploading all distributions, do publish again to upload the checksum +file: + +```sh +npm run release +```