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: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,7 +168,7 @@ We welcome code changes that improve this library or fix a problem, and please m
168
168
169
169
## Git flow & Release process
170
170
171
-
We enforce conventional commits and have an automated releasing process using lerna. Read our [git flow & release process guide](https://github.com/GetStream/stream-chat-react-native/blob/master/RELEASE_PROCESS.md) for more information
171
+
We enforce conventional commits and have an automated releasing process using workspaces and semantic-release. Read our [git flow & release process guide](https://github.com/GetStream/stream-chat-react-native/blob/master/RELEASE_PROCESS.md) for more information
Copy file name to clipboardExpand all lines: RELEASE_PROCESS.md
+3-4Lines changed: 3 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,8 @@
1
1
# Release process
2
2
3
-
## Lerna
3
+
## Workspaces & semantic-release
4
4
5
-
We use lerna to manage the release process for our SDK and SampleApp. It has an option for conventional commits and we use it on every commit and pull request
6
-
title so we can have automatically generated tags and changelogs.
5
+
We use workspaces and semantic-release to manage the release process for our SDK and SampleApp. It enforces conventional commits on every commit and pull request title so we can have automatically generated tags and changelogs.
7
6
8
7
## Angular conventional commits
9
8
@@ -12,7 +11,7 @@ Also, we enforce that our pull request titles follow the spec because we only co
12
11
13
12
## Creating breaking changes
14
13
15
-
Please follow [the spec](https://www.conventionalcommits.org/en/v1.0.0-beta.4/#commit-message-with-description-and-breaking-change-in-body) when adding breaking changes. Have in mind that the `!` in the commit message is not really supported from lerna yet so avoid that and just add the `BREAKING CHANGE:` flag to the commit body. As explained in the last section, you have two ways to trigger breaking changes: On commit level and on pull request level. The recommended is to do it at commit level in order to be more specific on whats breaking and which commits is generating the breaking change, but if thats not possible for some reason, you need to add it to the pull request merge body.
14
+
Please follow [the spec](https://www.conventionalcommits.org/en/v1.0.0-beta.4/#commit-message-with-description-and-breaking-change-in-body) when adding breaking changes. Have in mind that the `!` in the commit message is not really supported yet so avoid that and just add the `BREAKING CHANGE:` flag to the commit body. As explained in the last section, you have two ways to trigger breaking changes: On commit level and on pull request level. The recommended is to do it at commit level in order to be more specific on whats breaking and which commits is generating the breaking change, but if thats not possible for some reason, you need to add it to the pull request merge body.
0 commit comments