chore: make the latest release from release-v11 branch

.github/workflows/release.yml

@@ -24,7 +24,7 @@ jobs:
     name: Release from "${{ github.ref_name }}" branch
     runs-on: ubuntu-latest
     # GH does not allow to limit branches in the workflow_dispatch settings so this here is a safety measure
-    if: ${{ !inputs.docs_only && (github.ref_name == 'master' || github.ref_name == 'rc' || github.ref_name == 'release-v9') }}
+    if: ${{ !inputs.docs_only && startsWith(github.ref_name, 'release') || startsWith(github.ref_name, 'master') }}
     env:
       NODE_OPTIONS: --max_old_space_size=4096
     steps:
@@ -54,7 +54,7 @@ jobs:
     name: Publish documentation from "${{ github.ref_name }}" branch to ${{ inputs.docs_env }}
     runs-on: ubuntu-latest
     # skip during dry runs, release to production only from master, release to staging from anywhere
-    if: ${{ !inputs.dry_run && ((github.ref_name == 'master' && contains('production,staging', inputs.docs_env)) || (github.ref_name != 'master' && inputs.docs_env == 'staging')) }}
+    if: ${{ !inputs.dry_run && ((startsWith(github.ref_name, 'release') && contains('production,staging', inputs.docs_env)) || inputs.docs_env == 'staging') }}
     outputs:
       target-version: $${{ steps.target-version.outputs }}
     steps:

.releaserc.json

@@ -1,14 +1,20 @@
 {
   "branches": [
-    "main",
-    "master",
     {
-      "name": "beta",
+      "name": "master",
       "prerelease": true
     },
     {
-      "name": "rc",
-      "prerelease": true
+      "name": "release-v11",
+      "channel": "latest"
+    },
+    {
+      "name": "release-v10",
+      "range": "10.x"
+    },
+    {
+      "name": "release-v9",
+      "range": "9.x"
     }
   ],
   "plugins": [

developers/RELEASE.md

@@ -17,7 +17,7 @@ At the moment these manual actions have to be taken to achieve a successfull rel
 2. make sure that the peer dependencies `@stream-io/stream-chat-css` and `stream-chat-js` are installed at their latest version (see `package.json`, `yarn.lock`) (if applicable)
 3. squash-merge required pull requests to `master` branch with appropriate message name, for example: `fix(scope): new feature`, if this feature is breaking, make sure to include `BREAKING CHANGE: <reason>` in the message footer
 4. navigate to ["Actions"](https://github.com/GetStream/stream-chat-react/actions) and in the left bar select the "Release" workflow
-5. click "Run workflow" and select the branch you want to release from then adjust the prompt options and click "Run workflow", note that allowed branches for __PACKAGE RELEASE__ are: `master`, `release-v9` and `rc`, there's _is no such limititation_ for the __DOCUMENTATION RELEASE__, extend the workflow condition and `.releaserc.json` as needed
+5. click "Run workflow" and select the branch you want to release from then adjust the prompt options and click "Run workflow", note that allowed branches for __PACKAGE RELEASE__ are: branch names starting with `release` and `master`, there _is no such limititation_ for the __DOCUMENTATION RELEASE__, extend the workflow condition and `.releaserc.json` as needed. The `master` branch is the release-candidate branch.
 
 ## Available release prompt options