2a7210e382
* With ec29fd3e7b70953c7886af91ef840d54c46d166f, the prefix for the `bazel` command has been removed because it threw off the Bash variables. In order to fix this while still running Bazel from the `node_modules` (keeping the bazel versions consistent), we should run Bazel without Yarn (similar to how it's done for `build-packages-dist.sh`) PR Close #26899
23 lines
954 B
Bash
Executable File
23 lines
954 B
Bash
Executable File
#!/usr/bin/env bash
|
|
|
|
set -u -e -o pipefail
|
|
|
|
# Use for BETA and RC releases
|
|
# Query Bazel for npm_package and ng_package rules with tags=["release-with-framework"]
|
|
# Publish them to npm (tagged next)
|
|
|
|
# We need to resolve the Bazel binary in the node modules because running Bazel
|
|
# through `yarn bazel` causes additional output that throws off the command stdout.
|
|
BAZEL_BIN=$(yarn bin)/bazel
|
|
|
|
# query for all npm packages to be released as part of the framework release
|
|
NPM_PACKAGE_LABELS=`${BAZEL_BIN} query --output=label 'attr("tags", "\[.*release-with-framework.*\]", //packages/...) intersect kind(".*_package", //packages/...)'`
|
|
# build all npm packages in parallel
|
|
${BAZEL_BIN} build $NPM_PACKAGE_LABELS
|
|
# publish all packages in sequence to make it easier to spot any errors or warnings
|
|
for packageLabel in $NPM_PACKAGE_LABELS; do
|
|
echo "publishing $packageLabel"
|
|
${BAZEL_BIN} run -- ${packageLabel}.publish --access public --tag latest
|
|
done
|
|
|