Skip to content

docs: update release documentation regarding prerelease semver ranges #21590

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
clydin merged 1 commit into from
Aug 18, 2021
Merged

docs: update release documentation regarding prerelease semver ranges #21590

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/process/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,13 @@ In general, cherry picks for LTS should only be done if it meets one of the crit

Releasing is performed using Angular's unified release tooling. Each week, two releases are expected, `latest` and `next` on npm.

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 prerelease version segment.
For example, `"@angular/compiler-cli": "^13.0.0 || ^13.0.0-next"` in a prerelease should become `"@angular/compiler-cli": "^13.0.0"` in the stable release.
The current packages that require adjustment are:

- `@angular-devkit/build-angular`: packages/angular_devkit/build_angular/package.json
- `@ngtools/webpack`: packages/ngtools/webpack/package.json

To perform a release run the following and navigate the prompts:

```sh
Expand Down