Skip to content

docs: fold post-release version bump with the release commit #20958

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
filipesilva merged 1 commit into from
May 31, 2021
Merged

docs: fold post-release version bump with the release commit #20958

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
36 changes: 18 additions & 18 deletions docs/process/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,14 +55,16 @@ In general, cherry picks for LTS should only be done if it meets one of the crit

## Before releasing

Update `Angular` version in [`packages/schematics/angular/utility/latest-versions.ts`](https://github.com/angular/angular-cli/blob/master/packages/schematics/angular/utility/latest-versions.ts).
Update `Angular` version in
[`packages/schematics/angular/utility/latest-versions.ts`](https://github.com/angular/angular-cli/blob/master/packages/schematics/angular/utility/latest-versions.ts)
**and** [`package.json`](https://github.com/angular/angular-cli/blob/master/package.json).

## Shepparding

As commits are cherry-picked when PRs are merged, creating the release should be a matter of creating a tag.

```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 tag -a 'vXX' -m 'release: tag vXX'
```
Expand Down Expand Up @@ -153,23 +155,11 @@ using the `--githubToken` flag. You just then have to confirm the draft.

> **Tags containing `next` or `rc` should be marked as pre-release.**

## Post-release Version Update
## Post-release

**For each released version**:

Update `version` in root [`package.json`](/package.json#L3) to the _next_ release version.

```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/archives/C46U16D4Z) channel topic and also post
links to all the version bump PRs. If anyone else on the team notices these links missing, they should ask the caretaker
to make sure the post-release version bump is not forgotten.
Don't forget to update the Slack [#tools](https://angular-team.slack.com/archives/C46U16D4Z) channel
topic with the next caretaker shift from the
[calendar](https://calendar.google.com/calendar/embed?src=angular.io_jf53juok1lhpm84hv6bo6fmgbc%40group.calendar.google.com&ctz=America%2FLos_Angeles).

## Publishing a Major Version

Expand All @@ -190,3 +180,13 @@ packages.
```bash
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_jf53juok1lhpm84hv6bo6fmgbc%40group.calendar.google.com&ctz=America%2FLos_Angeles)
to modify shifts, **make sure you are logged in as your @angular.io account** and
click the "+ Google Calendar" button in the bottom right to add it to your Google
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.