From 8689e07caeff7d2c10120cdffc5db5fb1b24be32 Mon Sep 17 00:00:00 2001 From: Joey Perrott Date: Wed, 29 Apr 2020 12:40:52 -0700 Subject: [PATCH] build: use sh instead of exec for release scripts Previously the exec command was used, however the exec command would exit the original calling script regardless of the whether exit was called. This caused the release script to always exit after the pre-check phase. --- scripts/release/publish-latest | 2 +- scripts/release/publish-next | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/release/publish-latest b/scripts/release/publish-latest index 78aca6da0475f..3e3bafd9813a9 100755 --- a/scripts/release/publish-latest +++ b/scripts/release/publish-latest @@ -4,7 +4,7 @@ set -u -e -o pipefail # Runs the pre-check before performing the publish to ensure # the version is valid for release. -exec "$(dirname "$0")/pre-check"; +sh "$(dirname "$0")/pre-check"; # Use for production releases # Query Bazel for npm_package and ng_package rules with tags=["release-with-framework"] diff --git a/scripts/release/publish-next b/scripts/release/publish-next index 9b4e9743e778f..5a30b0db5d86c 100755 --- a/scripts/release/publish-next +++ b/scripts/release/publish-next @@ -4,7 +4,7 @@ set -u -e -o pipefail # Runs the pre-check before performing the publish to ensure # the version is valid for release. -exec "$(dirname "$0")/pre-check"; +sh "$(dirname "$0")/pre-check"; # Use for BETA and RC releases # Query Bazel for npm_package and ng_package rules with tags=["release-with-framework"]