luulam/AFFiNE
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity

docs: format releases.md

Browse Source
This commit is contained in:
himself65
2023-04-20 11:32:17 -05:00
parent 4d7a3e5bf1
commit 1e771131b0
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/contributing/releases.md
View File

@@ -13,13 +13,13 @@ Before releasing, ensure you have the latest version of the `master` branch.
And Read the semver specification to understand how to version your release. https://semver.org And Read the semver specification to understand how to version your release. https://semver.org
### 1. Update the version in `package.json.` ### 1. Update the version in `package.json`
```shell ```shell
yarn workspaces foreach exec yarn version 0.5.4-canary.5 yarn workspaces foreach exec yarn version 0.5.4-canary.5
``` ```
### 2. Commit changes and push to `master.` ### 2. Commit changes and push to `master`
```shel ```shel
git add . git add .
@@ -30,11 +30,11 @@ git push origin master
### 3. Create a release action ### 3. Create a release action
Create a release action in the [AFFiNE repository](https://github.com/toeverything/AFFiNE/actions/workflows/release-desktop-app.yml). Create a release action in the [Release Desktop App](https://github.com/toeverything/AFFiNE/actions/workflows/release-desktop-app.yml).
![img.png](assets/release-action.png) ![img.png](assets/release-action.png)
Select the correct branch and fill out the form, then click `Run workflow.` Select the correct branch and fill out the form, then click `Run workflow`.
### 4. Publish the release ### 4. Publish the release
@@ -42,6 +42,6 @@ After the release action is completed, you can see the draft release on the [rel
You can edit the release note and publish it. You can edit the release note and publish it.
Remember that the release tag and title should be the same as the version in `package.json.` Remember that the release tag and title should be the same as the version in `package.json`.
And target the release to that commit you just pushed. And target the release to that commit you just pushed.