From f2c55d01c43a3f766159cc0d1f07dc8efa361da9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicol=C3=B2=20Ribaudo?= Date: Thu, 21 Mar 2019 08:26:10 +0100 Subject: [PATCH] Create drafts instead of finished releases (#9729) [skip ci] Currently, the "Trigger GitHub release" and "Publish to npm" actions are run in parallel. Publishing to npm takes about 15 mins (it needs to run `make bootstrap`), so everyone watching the npm repo for releases would get the notification before that the new version is available on npm. This commit marks the automatically generated GitHub releases as draft, which then need to be manually "finalized" by real people. This will also avoid notifying people when for some reason a publish fails. --- .github/actions/trigger-github-release/release.js | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/actions/trigger-github-release/release.js b/.github/actions/trigger-github-release/release.js index 122696cfa7..1979f5e14d 100644 --- a/.github/actions/trigger-github-release/release.js +++ b/.github/actions/trigger-github-release/release.js @@ -18,6 +18,7 @@ getStdin() repo: repoName, tag_name: tag, body: changelog, + draft: true, })) .catch(err => { console.error(err);