zyycnandClaude 0c4da6c838 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>

2026-07-26 23:41:50 +08:00

..

_container.yml

chore(release): prepare v3.0.0

2026-07-25 01:54:18 +08:00

_quality.yml

ci: freeze applied migrations behind a sha256 manifest

2026-07-26 23:20:38 +08:00

ci.yml

ci: speed up validation pipelines

2026-07-16 16:07:55 +08:00

release.yml

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

2026-07-26 23:41:50 +08:00

security-scan.yml

chore(deps): bump setup-node to 7.0.0

2026-07-16 01:51:31 +08:00