Release 2026.3.8 升级实操：备份+ACP 来源标记+安全修复一次到位

问题/场景：升级时担心配置损坏、来源不可追踪、消息通道回归。前置条件：可在目标主机执行 OpenClaw CLI 且有维护窗口。实施步骤：1) 升级前执行 openclaw backup create 生成可恢复快照；2) 用 openclaw backup verify 校验备份完整性；3) 升级到 v2026.3.8 并重启 gateway；4) 按需启用 ACP provenance（meta 或 meta+receipt）；5) 验证 Telegram 去重与 cron 文本投递链路。关键命令：openclaw backup create/verify、openclaw gateway status。验证方法：备份可验证、升级后消息链路正常。风险与边界：不同平台回归项较多，生产需分批灰度。来源归因：GitHub Release + X 官方发布帖。

GITHUBDiscovered 2026-03-10Author openclaw maintainers

Prerequisites

You can execute OpenClaw CLI on the gateway host and restart service safely.
You have disk space and permission for local backup archives.

Steps

Create a pre-upgrade snapshot with openclaw backup create, and record the archive path.
Run openclaw backup verify against the created archive before touching runtime config.
Upgrade OpenClaw to v2026.3.8 via your standard change process and confirm gateway recovers.
If ACP agent binding is used, set provenance mode (meta or meta+receipt) and verify receipt visibility in messages.
Run targeted smoke tests for Telegram DM dedupe and cron announce text delivery.

Commands

openclaw backup create

openclaw backup verify <backup-path>

openclaw gateway status

openclaw gateway restart

Verify

Backup verifies successfully, gateway status is healthy post-upgrade, and Telegram/cron message paths deliver once without duplicates.

Caveats

Release notes aggregate many fixes; verify only the features you actually depend on before full rollout.
ACP provenance metadata visibility may vary by client rendering and channel bridge（需验证）.

Source attribution

This tip is aggregated from community/public sources and preserved with attribution.

Open original source ↗

Visit original post