docs: updates release documentation to include latest-versions/package.json and clarify what can be done in the release PR

This commit is contained in:
Doug Parker 2022-11-16 10:35:32 -08:00 committed by Douglas Parker
parent 3f17fb806f
commit 99b258d929

View File

@ -74,6 +74,7 @@ Releasing is performed using Angular's unified release tooling. Each week, two r
After FW releases `-rc.0` for an upcoming minor/major version, update the corresponding version in:
- [`latest-versions.ts`](/packages/schematics/angular/utility/latest-versions.ts#L=18)
- [`latest-versions/package.json`](/packages/schematics/angular/utility/latest-versions/package.json)
- [`@angular-devkit/build-angular`](/packages/angular_devkit/build_angular/package.json)
- [`@ngtools/webpack`](/packages/ngtools/webpack/package.json)
@ -86,18 +87,7 @@ which lands after FW releases (or else CI will fail) but _before_ the CLI releas
built before the PR is sent for review, so any changes after that point won't be included in the
release.
**For a major release:**
**As part of the release PR**, make sure to:
- modify
[`latest-versions.ts`](https://github.com/angular/angular-cli/blob/main/packages/schematics/angular/utility/latest-versions.ts#L18)
so the Angular semver is updated from `~13.0.0-rc` to just `~13.0.0`.
- This is the version generated in `ng new` schematics and needs to be updated to avoid having
users generate projects with `-rc` in the dependencies.
- update the
[`ng-packagr`](https://github.com/angular/angular-cli/blob/main/packages/schematics/angular/utility/latest-versions/package.json#L15)
dependency to a stable version (ex. from `^13.0.0-next.0` to `^13.0.0`).
**Following a major release:**
When a release is transitioning from a prerelease to a stable release, the semver ranges for Angular
dependencies within the packages' `package.json` files will need to be updated to remove the