v2026.2.19 升级清单：设备配对清理、relay 鉴权收口与 cron topic 修复
问题/场景：多设备配对和 Telegram 话题投递在旧版本易出现脏状态或投递偏移。前置：可维护升级窗口、可执行 CLI 管理命令。实施步骤：升级到 v2026.2.19 后先做配对卫生清理，再验证 relay token 鉴权与 cron topic 投递。关键命令：`openclaw devices remove`、`openclaw devices clear --yes --pending`。验证：设备列表干净、topic 定向消息落在目标线程。风险：批量清理设备前需确认在用节点，避免误删。来源：官方 release notes。
GITHUBDiscovered 2026-02-20Author openclaw
Prerequisites
- You can upgrade OpenClaw and restart gateway during a planned maintenance window.
- You know which paired devices are active and which are stale/pending.
Steps
- Upgrade to v2026.2.19, then verify daemon health (`openclaw gateway status`) before making cleanup changes.
- Run paired-device hygiene: remove known-stale entries and optionally clear pending requests with explicit `--yes` guard.
- Re-check relay auth path using gateway token for extension/CDP access; ensure old unauth flows are not relied upon.
- Create a Telegram cron/heartbeat test targeting a specific topic and confirm delivery lands in that topic thread.
- Document the post-upgrade state (removed devices, remaining active nodes, test results) for rollback traceability.
Commands
openclaw gateway statusopenclaw devices remove <deviceId>openclaw devices clear --yes --pendingopenclaw cron listVerify
After upgrade, stale pairings are removed, relay requires token auth, and topic-scoped scheduled messages route correctly.
Caveats
- `devices` subcommands depend on version; confirm syntax with `openclaw help` before production execution（需验证）.
- Bulk clear can remove still-needed pending requests; snapshot state before cleanup.
Source attribution
This tip is aggregated from community/public sources and preserved with attribution.
Open original source ↗