angular/dev-infra/release
Paul Gschwendtner 5947239f89 fix(dev-infra): do not set lts dist tag on packages from release-candidate train (#41946)
Currently if a major release-train in the `release-candidate`/`feature-freeze`
phase becomes `latest`, we intend to set the NPM LTS dist tag for all packages
of the previous major (as the old release train in `latest` moves into LTS phase).

The logic for this exists but the release tool sets the NPM dist tag for
all packages of the new major. This means that the script might error if
a new package is part of the new major; or it could cause a deleted
package to not receive the LTS tag properly.

PR Close #41946
2021-05-04 21:07:57 -07:00
..
build fix(dev-infra): update type castings for JSON.parse usage (#40710) 2021-02-09 10:48:43 -08:00
config feat(dev-infra): create ReleaseNotes class for generating release notes during publishing (#41476) 2021-04-09 07:49:48 -07:00
publish fix(dev-infra): do not set lts dist tag on packages from release-candidate train (#41946) 2021-05-04 21:07:57 -07:00
set-dist-tag refactor(dev-infra): create ng-dev executable locally in the repo (#39089) 2020-10-22 13:36:14 -07:00
stamping refactor(dev-infra): move getRepoBaseDir() to GitClient (#41527) 2021-04-15 11:28:12 -07:00
versioning fix(dev-infra): update type castings for JSON.parse usage (#40710) 2021-02-09 10:48:43 -08:00
BUILD.bazel feat(dev-infra): support --mode flag for building environment stamp (#40095) 2020-12-15 13:36:56 -08:00
cli.ts feat(dev-infra): support --mode flag for building environment stamp (#40095) 2020-12-15 13:36:56 -08:00