"Fossies" - the Fresh Open Source Software Archive  

Source code changes of the file "docs/process/release.md" between
angular-cli-12.0.3.tar.gz and angular-cli-12.0.4.tar.gz

About: Angular CLI is a command line interface for Angular.

release.md  (angular-cli-12.0.3):release.md  (angular-cli-12.0.4)
skipping to change at line 58 skipping to change at line 58
1. It addresses a critical security vulnerability. 1. It addresses a critical security vulnerability.
2. It fixes a breaking change in the external environment. 2. It fixes a breaking change in the external environment.
For example, this could happen if one of the dependencies is deleted from NPM . For example, this could happen if one of the dependencies is deleted from NPM .
3. It fixes a legitimate failure on CI for a particular LTS branch. 3. It fixes a legitimate failure on CI for a particular LTS branch.
# Release # Release
## Before releasing ## Before releasing
Update `Angular` version in [`packages/schematics/angular/utility/latest-version Update `Angular` version in
s.ts`](https://github.com/angular/angular-cli/blob/master/packages/schematics/an [`packages/schematics/angular/utility/latest-versions.ts`](https://github.com/an
gular/utility/latest-versions.ts). gular/angular-cli/blob/master/packages/schematics/angular/utility/latest-version
s.ts)
**and** [`package.json`](https://github.com/angular/angular-cli/blob/master/pack
age.json).
## Shepparding ## Shepparding
As commits are cherry-picked when PRs are merged, creating the release should be a matter of creating a tag. As commits are cherry-picked when PRs are merged, creating the release should be a matter of creating a tag.
```bash ```bash
git add packages/schematics/angular/utility/latest-versions.ts git add packages/schematics/angular/utility/latest-versions.ts package.json
git commit -m 'release: vXX' git commit -m 'release: vXX'
git tag -a 'vXX' -m 'release: tag vXX' git tag -a 'vXX' -m 'release: tag vXX'
``` ```
The package versions we are about to publish are derived from `version` in the r oot The package versions we are about to publish are derived from `version` in the r oot
[`package.json`](https://github.com/angular/angular-cli/blob/master/package.json #L3). Double check that the versions are correct by running the [`package.json`](https://github.com/angular/angular-cli/blob/master/package.json #L3). Double check that the versions are correct by running the
following command. following command.
```bash ```bash
yarn admin packages --releaseCheck yarn admin packages --releaseCheck
skipping to change at line 156 skipping to change at line 158
Copy the output (you can use `| pbcopy` on MacOS or `| xclip` on Linux) and Copy the output (you can use `| pbcopy` on MacOS or `| xclip` on Linux) and
paste the release notes on [GitHub](https://github.com/angular/angular-cli/relea ses) paste the release notes on [GitHub](https://github.com/angular/angular-cli/relea ses)
for the tag just released. for the tag just released.
If you have an API token for GitHub you can create a draft automatically by If you have an API token for GitHub you can create a draft automatically by
using the `--githubToken` flag. You just then have to confirm the draft. using the `--githubToken` flag. You just then have to confirm the draft.
> **Tags containing `next` or `rc` should be marked as pre-release.** > **Tags containing `next` or `rc` should be marked as pre-release.**
## Post-release Version Update ## Post-release
**For each released version**: Don't forget to update the Slack [#tools](https://angular-team.slack.com/archive
s/C46U16D4Z) channel
Update `version` in root [`package.json`](/package.json#L3) to the _next_ releas topic with the next caretaker shift from the
e version. [calendar](https://calendar.google.com/calendar/embed?src=angular.io_jf53juok1lh
pm84hv6bo6fmgbc%40group.calendar.google.com&ctz=America%2FLos_Angeles).
```sh
git checkout -b release-bump-vXX
git commit package.json packages/schematics/angular/utility/latest-versions.ts -
m "build: bump version to vXX"
git push -u origin release-bump-vXX
```
Then make a PR and assign it to the next primary caretaker.
Don't forget to update the Slack [#tools](https://angular-team.slack.com/archive
s/C46U16D4Z) channel topic and also post
links to all the version bump PRs. If anyone else on the team notices these link
s missing, they should ask the caretaker
to make sure the post-release version bump is not forgotten.
## Publishing a Major Version ## Publishing a Major Version
For the first release of a major version, say `v10.0.0`, checkout the major bran ch For the first release of a major version, say `v10.0.0`, checkout the major bran ch
(i.e. `10.0.x`), then run: (i.e. `10.0.x`), then run:
```bash ```bash
yarn # Reload dependencies yarn # Reload dependencies
yarn admin publish --tag next # a major release is always tagged as next initial ly yarn admin publish --tag next # a major release is always tagged as next initial ly
``` ```
Confirm with downstream repositories (Components, etc) that everything is ok. Confirm with downstream repositories (Components, etc) that everything is ok.
Once the release is stable, wait for Framework to retag their packages, then Once the release is stable, wait for Framework to retag their packages, then
retag the CLI packages as `latest`. retag the CLI packages as `latest`.
The command below will automatically retag stable packages as well as experiment al The command below will automatically retag stable packages as well as experiment al
packages. packages.
```bash ```bash
yarn admin dist-tag --version 10.0.0 --tag latest yarn admin dist-tag --version 10.0.0 --tag latest
``` ```
## Changing shifts
If you need to update the
[caretaker calendar](https://calendar.google.com/calendar/embed?src=angular.io_j
f53juok1lhpm84hv6bo6fmgbc%40group.calendar.google.com&ctz=America%2FLos_Angeles)
to modify shifts, **make sure you are logged in as your @angular.io account** an
d
click the "+ Google Calendar" button in the bottom right to add it to your Googl
e
Calendar account. You should then be able to find and modify events on
calendar.google.com. The calendar is a part of the `angular.io` organization, so
events can only be modified by users in the same organization.
 End of changes. 5 change blocks. 
24 lines changed or deleted 13 lines changed or added

Home  |  About  |  Features  |  All  |  Newest  |  Dox  |  Diffs  |  RSS Feeds  |  Screenshots  |  Comments  |  Imprint  |  Privacy  |  HTTP(S)