diff --git a/.github/workflows/create-release.yml b/.github/workflows/create-release.yml
index ffb42b2ac..37513b04a 100644
--- a/.github/workflows/create-release.yml
+++ b/.github/workflows/create-release.yml
@@ -30,14 +30,6 @@ jobs:
       contents: write
       pull-requests: write
     steps:
-      - name: Validate branch for latest release
-        if: inputs.release_type == 'latest' && github.ref_name != 'main'
-        run: |
-          echo "👹 Oops! Cannot release 'latest' from branch '${{ github.ref_name }}'!"
-          echo "💡 The 'latest' release type can only be created from the 'main' branch."
-          echo "💡 Maintenance branches should use 'stable' instead."
-          exit 1
-
       - name: Checkout Repo
         uses: actions/checkout@v6
         with:
diff --git a/docs/package-release.md b/docs/package-release.md
index e58a97a23..7f337183f 100644
--- a/docs/package-release.md
+++ b/docs/package-release.md
@@ -218,7 +218,11 @@ git push origin chore/v1.0.0
 
 ### Promoting to stable release
 
-Stable releases are created from `chore/v*` branches. Once a stable release is published, the pre-release mode is switched off and `main` must be updated to reflect the version bump and exit from pre-release mode.
+Stable releases (`stable` or `latest`) can be created from `chore/v*` branches. Once released, the pre-release mode is switched off and `main` must be updated to reflect the version bump and exit from pre-release mode.
+
+> [!WARNING]
+> Use `latest` only when you want this version to become the **default** installed by `npm install @clickhouse/click-ui`.
+> Publishing `latest` from an older maintenance branch (e.g., `chore/v1.x.x`) **will downgrade** the default for all users who haven't pinned a version, even if a newer `v2.x.x` was previously `latest`.
 
 Follow these steps:
 
@@ -226,7 +230,7 @@ Follow these steps:
 
 2. Run the [Create Release](https://github.com/ClickHouse/click-ui/actions/workflows/create-release.yml) workflow from the `chore/v*` branch:
    - Select the maintenance branch (e.g., `chore/v1.0.0`)
-   - Choose `stable` as the release type
+   - Choose `stable` or `latest` as the release type
    - Confirm the release type and branch name
 
 3. Review and merge the release PR into the maintenance branch