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
..
configure-next-as-major.ts	feat(dev-infra): tool for staging and publishing releases (#38656)	2020-09-28 16:11:42 -04:00
cut-lts-patch.ts	refactor(dev-infra): improve type safety of NPM dist tags in release tool (#42133)	2021-05-18 14:04:14 -07:00
cut-new-patch.ts	feat(dev-infra): include release notes in Github release entries when publishing (#41964)	2021-05-06 15:45:48 -04:00
cut-next-prerelease.ts	feat(dev-infra): include release notes in Github release entries when publishing (#41964)	2021-05-06 15:45:48 -04:00
cut-release-candidate.ts	feat(dev-infra): include release notes in Github release entries when publishing (#41964)	2021-05-06 15:45:48 -04:00
cut-stable.ts	feat(dev-infra): publish major versions to "next" NPM dist tag (#42133)	2021-05-18 14:04:14 -07:00
index.ts	feat(dev-infra): publish major versions to "next" NPM dist tag (#42133)	2021-05-18 14:04:14 -07:00
move-next-into-feature-freeze.ts	feat(dev-infra): include release notes in Github release entries when publishing (#41964)	2021-05-06 15:45:48 -04:00
tag-recent-major-as-latest.ts	feat(dev-infra): publish major versions to "next" NPM dist tag (#42133)	2021-05-18 14:04:14 -07:00