Paul Gschwendtner 9d75687f62 feat(dev-infra): publish major versions to "next" NPM dist tag (#42133) ... 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		2021-05-18 14:04:14 -07:00
..
build	feat(dev-infra): Set up new common release notes generation tooling (#41905)	2021-05-06 09:40:29 -04:00
config	test(dev-infra): add testing for integration of ReleaseNotes in publishing tooling (#41967)	2021-05-14 21:07:27 +00:00
publish	feat(dev-infra): publish major versions to "next" NPM dist tag (#42133)	2021-05-18 14:04:14 -07:00
set-dist-tag	feat(dev-infra): Set up new common release notes generation tooling (#41905)	2021-05-06 09:40:29 -04:00
stamping	refactor(dev-infra): move `getRepoBaseDir()` to `GitClient` (#41527)	2021-04-15 11:28:12 -07:00
versioning	refactor(dev-infra): improve type safety of NPM dist tags in release tool (#42133)	2021-05-18 14:04:14 -07: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