L4 0.2.2

Owners of Git-connected Cloudflare Servers can now update from Settings → Deployment → Updates. Choose a newer published release and select Back up and update. Stable releases are shown by default; prereleases require an explicit opt-in.

• Save a mandatory pre-update database and files backup to the separate backup bucket. Before deployment, the Git Build downloads the persisted archive, verifies its hash, restores SQLite, checks Server identity and foreign keys, and compares community data and files against the running Server. A failed backup check stops the update.
• Run updates exclusively through the Server's Git-connected Cloudflare Build. The Server holds a narrow deploy hook rather than account deployment credentials. Existing resource bindings, encryption secrets, Server UUID, Accounts and content are preserved.
• Keep progress on the Server when the browser closes. Serialize concurrent requests, allow queued cancellation/retry, and require a stopped preceding Build before recovering an interrupted or ambiguous deployment. No automatic downgrade or destructive rollback is introduced.
• Configure hooks automatically for new Cloudflare installs. Ordinary Builds leave an existing Server unchanged without an explicit Owner update request.
• Report the same installed version in public discovery, health and update settings.

Existing Servers need one operator-managed, backed-up update to 0.2.2 and a one-time Build hook connection before subsequent releases can be installed from Settings. See Server updates. This release appends migration 0001_server_updates.sql for the private operation journal; the published server-v1 baseline remains unchanged. Restored backups clear the operation and one-job capability while preserving the encrypted hook.

The backup check is optimistic, rather than an atomic D1/R2 snapshot; keep Server activity low while it runs. Preserve environment secrets separately. Backup buckets and archives remain separate from live files and survive later Server removal.

The official site, Shell, standalone Server, portable amd64 runtime, VPS installer and version-pinned Docs share version 0.2.2. VPS/celld retains its documented operator-managed llll upgrade workflow and experimental verification limits. Native iOS/macOS packaging remains frozen.