From b8259a82c1f59167b5dfcbc1d60ca2041d77d784 Mon Sep 17 00:00:00 2001 From: Charles Kerr Date: Tue, 5 Dec 2017 08:38:16 -0600 Subject: [PATCH] note that 'npm run release -- --validateRelease' must be run in release branch --- docs/development/releasing.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/docs/development/releasing.md b/docs/development/releasing.md index d8cda864507e..f2baa345bd16 100644 --- a/docs/development/releasing.md +++ b/docs/development/releasing.md @@ -202,8 +202,12 @@ release notes. leave it checked for beta releases. 4. Click 'Save draft'. **Do not click 'Publish release'!** 5. Wait for all builds to pass before proceeding. -6. You can run `npm run release -- --validateRelease` to verify that all of the -required files have been created for the release. +6. In the `release` branch, verify that the release's files have been created: +```sh +$ git rev-parse --abbrev-ref HEAD +release +$ npm run release -- --validateRelease +``` ## Merge temporary branch Once the release builds have finished, merge the `release` branch back into