openclaw-upgradelisted

# OpenClaw Safe Upgrade Kcn runs a live automated trading system on OpenClaw. An upgrade that loses crons, breaks embeddings, or orphans an in-flight cron is a production incident. This is the battle-tested flow (5.28→6.1→6.5→6.6→6.8). Full version-specific history lives in auto-memory `openclaw-update-missing-deps.md` — read it first for the target version's known traps. ## 0. Check + decide 1. `openclaw --version` vs `npm view openclaw version` (latest). Pull the changelog (`npm pack openclaw@<v>` → `package/CHANGELOG.md`) and judge relevance — don't upgrade reflexively. 2. Read auto-memory `openclaw-update-missing-deps.md` for that version's traps. ## 1. 🔴 Never restart the gateway while a cron is in-flight Use the structured runtime field, not a text grep: ```bash openclaw cron list --json \ | jq -e '[.jobs[] | select(.state.runningAtMs != null)] | length == 0' ``` If this is not `true`, wait. A SIGTERM mid-run can orphan the cron into permanent `running`. Use `--no-restart` and pick a quiet window between slots (`bash ops/host/check_crons.sh --timeline`). ## 2. Update (built-in updater, since 6.x) ``` openclaw update --tag <version> --no-restart --yes ``` This auto-reinstalls/links managed plugins (weixin, llama-cpp, codex) — no manual `pnpm add`, no systemd edits, no `restore-llama-embeddings.sh` needed. (Pre-6.x manual flow is in the memory file.) ## 3. 🔴 Reapply all upgrade-sensitive local patches before restart The updater replaces the installed `dist/` tr