chore: change default branch to canary (#4948)

docs/CONTRIBUTING.md

@@ -13,7 +13,7 @@ Use the table of contents icon on the top left corner of this document to get to
 Currently we have two versions of AFFiNE:
 
 - [AFFiNE Pre-Alpha](https://livedemo.affine.pro/). This version uses the branch `Pre-Alpha`, it is no longer actively developed but contains some different functions and features.
-- [AFFiNE Alpha](https://pathfinder.affine.pro/). This version uses the `master` branch, this is the latest version under active development.
+- [AFFiNE Alpha](https://pathfinder.affine.pro/). This version uses the `canary` branch, this is the latest version under active development.
 
 To get an overview of the project, read the [README](../README.md). Here are some resources to help you get started with open source contributions:
 

docs/contributing/releases.md

@@ -11,7 +11,7 @@ The AFFiNE core team gives release authorization. And also have the following re
 
 ## How to make a release?
 
-Before releasing, ensure you have the latest version of the `master` branch.
+Before releasing, ensure you have the latest version of the `canary` branch.
 
 And Read the semver specification to understand how to version your release. https://semver.org
 
@@ -21,13 +21,13 @@ And Read the semver specification to understand how to version your release. htt
 ./scripts/set-version.sh 0.5.4-canary.5
 ```
 
-### 2. Commit changes and push to `master`
+### 2. Commit changes and push to `canary`
 
 ```shell
 git add .
 # vx.y.z-canary.n
 git commit -m "v0.5.4-canary.5"
-git push origin master
+git push origin canary
 ```
 
 ### 3. Create a release action