Skip to content

Commit b9ed17a

Browse files
authored
docs: create a release doc
Outlining release steps
1 parent 044856f commit b9ed17a

File tree

1 file changed

+36
-0
lines changed

1 file changed

+36
-0
lines changed

docs/process/release.md

+36
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
# Release Steps
2+
- Login as `angular` npm account
3+
- Update the version in `package.json` - [Example Commit](https://github.com/angular/universal/commit/fccca4b49f198fb9b6a52877db58909ebb419369)
4+
- Create a release commit
5+
```sh
6+
git commit -a -m "release: v9.0.0-next.13" # (Update to version just put in package.json)
7+
```
8+
- Create a tag
9+
```sh
10+
git tag -v v9.0.0-next.13
11+
```
12+
- Push commit and tag
13+
```sh
14+
git push upstream && git push upstream --tags
15+
```
16+
- Publish
17+
```sh
18+
# For release with 'next' tag
19+
./publish-next.sh
20+
```
21+
22+
```sh
23+
# For release with 'latest' tag
24+
./publish.sh
25+
```
26+
27+
# Release Changelog
28+
(TODO: Borrow the changelog from Angular CLI project. For now use these simple instructions)
29+
- Get commits between the two releases
30+
```sh
31+
git log v9.0.0-next.12..v9.0.0-next.13 | xclip -selection clipboard
32+
```
33+
- Go to the `Releases` tab in the repository
34+
- Click on the newly created tag (9.0.0-next.13 in this case)
35+
- Paste the contents of clipboard to the contents
36+
- Choose `This is a prerelase` checkbox for pre-release versions

0 commit comments

Comments
 (0)