docs: warn 2.x deployments that 3.x is a clean break

The runtime cross-major gate only exists in 3.x binaries; a 2.x admin UI
happily offers the one-click update that produces a non-starting service.
State the clean break in the three places a 2.x operator actually sees
before upgrading: the top of every 3.x GitHub Release body, the README
operations section, and the deploy README upgrade section, each with the
fresh-deployment path (new .runtime/, re-import or re-authorize accounts
and client keys).

Co-authored-by: Claude <noreply@anthropic.com>
This commit is contained in:
zyycn
2026-07-26 23:41:50 +08:00
co-authored by Claude
parent 225c1166c6
commit 0c4da6c838
3 changed files with 16 additions and 0 deletions
+3
View File
@@ -629,6 +629,9 @@ jobs:
prerelease: ${{ needs.release-info.outputs.prerelease == 'true' }}
make_latest: ${{ needs.release-info.outputs.prerelease == 'true' && 'false' || 'true' }}
body: |
> [!WARNING]
> **Upgrading from 2.x?** 3.x is a clean break: the 2.x database schema and configuration are not migrated, and the one-click self-update cannot cross major versions — do not trigger it from a 2.x admin UI. Deploy 3.x fresh (new `.runtime/` data directory) and re-import or re-authorize provider accounts and client keys. See the [upgrade notes](https://github.com/${{ github.repository }}/blob/main/deploy/README.md#镜像升级与源码构建).
## 📥 Installation
**Docker:**