You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/process/release.md
+3-13Lines changed: 3 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,24 +69,14 @@ Releasing is performed using Angular's unified release tooling. Each week, two r
69
69
70
70
Once FW releases the actual minor/major release (for example: `13.0.0` or `13.1.0`), update dependencies with the following:
71
71
72
-
1. Run `sed -i -E "s, \|\| \^13\.1\.0-(next|rc)\.[0-9]+,,g" packages/**/package.json` with the release version to remove prerelease tags.
73
-
- No need to update `devDependencies` in the root `package.json`, Renovate will get them later.
74
-
2. Update [`latest-versions/package.json`](packages/schematics/angular/utility/latest-versions/package.json) so `@angular/core` and `ng-packagr` are using the release version (drop `-rc.0` / `-next.0`).
75
-
- This is the file used by `ng new` to determine versions in the generated `package.json` seen by developers.
76
-
3. Run `yarn -s bazel run @npm2//:sync` to update the pnpm lockfile.
72
+
1. Update [`constants.bzl`](../../constants.bzl) so `@angular/core` and `ng-packagr` are using the release version (drop `-next.0`).
77
73
78
-
Merge the above two changes in a separate PR which lands _after_ FW releases (or else CI will fail) but _before_ the CLI
74
+
Merge the above change in a separate PR which lands _after_ FW releases (or else CI will fail) but _before_ the CLI
79
75
release PR. Releases are built before the PR is sent for review, so any changes after that point won't be included in the release.
80
76
81
-
**AFTER a major CLI release:**
82
-
83
-
Once a major release is complete, peer dependencies in the above files will need to be updated to "undo" the above change and add the
84
-
prerelease version segment on `main`. For example, `"@angular/compiler-cli": "^13.0.0-next.0"` should become
85
-
`"@angular/compiler-cli": "^13.0.0 || ^13.1.0-next.0"`. This should be done for all the peer deps in the above files.
86
-
87
77
**AFTER a minor OR major CLI release:**
88
78
89
-
`latest-versions.ts` also needs to be updated to use `-next.0` after a major or minor release. However this needs to happen _after_ FW
79
+
`constants.bzl` also needs to be updated to use `-next.0` after a major or minor release. However this needs to happen _after_ FW
90
80
publishes the initial `-next.0` release, which will happen 1 week after the major or minor release.
0 commit comments