7fb8527e1e
Currently the ng-dev release tool always run `bazel clean` before calling the configured build release function. The clean is necessary to ensure the release output is actually built; and not restored from previous builds which could have different bazel workspace status variables (which provide the NPM package version). Instead of doing this as part of the release tool, the actual script running to build the release output should run the `bazel clean`. The release tool does not intend to know about details on how the release output is built. This is necessary because the build setup could vary between version branches (especially for older ones; such as LTS version branches). PR Close #42101 |
||
|---|---|---|
| .. | ||
| browserstack | ||
| build | ||
| ci | ||
| github | ||
| local-dev | ||
| release | ||
| build-package-dist.js | ||
| compare-master-to-patch.js | ||
| puppeteer-chromedriver-versions.js | ||
| webdriver-manager-update.js | ||