docs: clarify update diagnostics · openclaw/openclaw@3147efb
steipete
·
2026-05-04
·
via Recent Commits to openclaw:main
| Original file line number | Diff line number | Diff line change |
|---|
@@ -2,6 +2,7 @@
|
2 | 2 | summary: "CLI reference for `openclaw update` (safe-ish source update + gateway auto-restart)" |
3 | 3 | read_when: |
4 | 4 | - You want to update a source checkout safely |
| 5 | + - You are debugging `openclaw update` output or options |
5 | 6 | - You need to understand `--update` shorthand behavior |
6 | 7 | title: "Update" |
7 | 8 | --- |
@@ -42,6 +43,14 @@ openclaw --update
|
42 | 43 | - `--timeout <seconds>`: per-step timeout (default is 1800s). |
43 | 44 | - `--yes`: skip confirmation prompts (for example downgrade confirmation). |
44 | 45 | |
| 46 | +`openclaw update` does not have a `--verbose` flag. Use `--dry-run` to preview |
| 47 | +the planned channel/tag/install/restart actions, `--json` for machine-readable |
| 48 | +results, and `openclaw update status --json` when you only need channel and |
| 49 | +availability details. If you are debugging Gateway logs around an update, |
| 50 | +console verbosity and file log level are separate: Gateway `--verbose` affects |
| 51 | +terminal/WebSocket output, while file logs require `logging.level: "debug"` or |
| 52 | +`"trace"` in config. See [Gateway logging](/gateway/logging). |
| 53 | + |
45 | 54 | <Warning> |
46 | 55 | Downgrades require confirmation because older versions can break configuration. |
47 | 56 | </Warning> |
|
| Original file line number | Diff line number | Diff line change |
|---|
@@ -25,6 +25,12 @@ openclaw update --tag main
|
25 | 25 | openclaw update --dry-run # preview without applying |
26 | 26 | ``` |
27 | 27 | |
| 28 | +`openclaw update` does not accept `--verbose`. For update diagnostics, use |
| 29 | +`--dry-run` to preview the planned actions, `--json` for structured results, or |
| 30 | +`openclaw update status --json` to inspect channel and availability state. The |
| 31 | +installer has its own `--verbose` flag, but that flag is not part of |
| 32 | +`openclaw update`. |
| 33 | + |
28 | 34 | `--channel beta` prefers beta, but the runtime falls back to stable/latest when |
29 | 35 | the beta tag is missing or older than the latest stable release. Use `--tag beta` |
30 | 36 | if you want the raw npm beta dist-tag for a one-off package update. |
|
此内容由惯性聚合(RSS阅读器)自动聚合整理，仅供阅读参考。 原文来自 — 版权归原作者所有。
