build: use sh instead of exec for release scripts (#36862)
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. PR Close #36862
This commit is contained in:
parent
3d82aa781d
commit
cebd4fada7
|
@ -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"]
|
||||
|
|
|
@ -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"]
|
||||
|
|
Loading…
Reference in New Issue