5947239f89
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 |
||
|---|---|---|
| .. | ||
| configure-next-as-major.ts | ||
| cut-lts-patch.ts | ||
| cut-new-patch.ts | ||
| cut-next-prerelease.ts | ||
| cut-release-candidate.ts | ||
| cut-stable.ts | ||
| index.ts | ||
| move-next-into-feature-freeze.ts | ||