|
23 | 23 | # Manual release steps (Updated on 2024-02-08)
|
24 | 24 | 1. At main branch, make sure everything is ready to deployment.
|
25 | 25 | 2. Checkout release branch `git checkout -b release/{X.X.X}`.
|
26 |
| -3. In the branche update two files: |
| 26 | +3. In the branch update two files: |
27 | 27 | - In `package.json`, update new version.
|
28 | 28 | - In `CHANGELOG.md`, add a new changelog.
|
29 | 29 | 5. Commit and push to the branch.
|
|
33 | 33 | - Update changelog link to the correct path: `CHANGELOG.md`.
|
34 | 34 | - Add all merged [SBISSUES tickets](https://sendbird.atlassian.net/jira/dashboards/11202?maximized=25045) in the `Linked issues` as `blocks` (When the ticket status changes to `Released`, Atlassan automatically adds a comment to each linked issues).
|
35 | 35 | 8. Ask EM to review the release ticket and await for `Release approved`.
|
36 |
| -9. In the release branch, create a new tag `v{X.X.X}` and the push the tag `git push v{X.X.X} origin` |
37 |
| -10. In the root, `yarn build` to create new build files. Once created, make sure files in `dist` is newly created/updated. |
38 |
| -11. Change directory to `./dist` and then publish `npm publish` |
| 36 | +9. In the root, `yarn build` to create new build files. Once created, make sure files in `dist` is newly created/updated. |
| 37 | +10. Change directory to `./dist` and then publish `npm publish` |
| 38 | +11. In the release branch, create a new tag `v{X.X.X}` and the push the tag `git push v{X.X.X} origin`. |
39 | 39 | 12. After release do the followings:
|
40 | 40 | - Update release ticket to `Released`
|
41 | 41 | - In the [releases](https://github.com/sendbird/sendbird-uikit-react/releases) draft a new release note with the new tag (write changelog in the description) and then publish release.
|
42 |
| - - In the `sdk-release`, post a release message. |
| 42 | + - In the `sdk-release`, post a release message. |
0 commit comments