f96dcc5ce0
Creates a tool for staging and publishing releases as per the new branching and versioning that has been outlined in the following document. The tool is intended to be used across the organization to ensure consistent branching/versioning and labeling: https://docs.google.com/document/d/197kVillDwx-RZtSVOBtPb4BBIAw0E9RT3q3v6DZkykU/edit#heading=h.s3qlps8f4zq7dd The tool implements the actions as outlined in the following initial plan: https://hackmd.io/2Le8leq0S6G_R5VEVTNK9A. The implementation slightly diverged in so far that it performs staging and publishing together so that releasing is a single convenient command. In case of errors for which re-running the full command is not sufficient, we want to consider adding recover functionality. e.g. when the staging completed, but the actual NPM publishing aborted unexpectedly due to build errors. PR Close #38656 |
||
---|---|---|
.. | ||
BUILD.bazel | ||
README.md | ||
active-release-trains.ts | ||
inc-semver.ts | ||
index.ts | ||
long-term-support.ts | ||
next-prerelease-version.ts | ||
npm-publish.ts | ||
npm-registry.ts | ||
print-active-trains.ts | ||
release-trains.ts | ||
version-branches.ts |
README.md
Versioning for the Angular organization
The folder contains common tooling needed for implementing the versioning as proposed by this design document. Primary tooling is the determination of active release trains.