9d75687f62
Previously, the dev-infra release tool would publish major versions directly to the NPM `@latest` dist tag. This is correct in theory, but rather unpractical given that we want to publish packages first as `@next` so that other dependent Angular packages can update too, allowing us to publish all main Angular packages (from FW, COMP and TOOL) at the same time to `@latest` on NPM. This involves creating a new release action for re-tagging the previously released major as `@latest` on NPM. PR Close #42133 |
||
|---|---|---|
| .. | ||
| build | ||
| config | ||
| publish | ||
| set-dist-tag | ||
| stamping | ||
| versioning | ||
| BUILD.bazel | ||
| cli.ts | ||