docs: record upgrade recovery fixes

This commit is contained in:
Peter Steinberger
2026-05-03 21:39:49 +01:00
parent 797d02497e
commit 3301760567
3 changed files with 12 additions and 6 deletions

View File

@@ -116,10 +116,12 @@ service, and verify the restarted Gateway reports the expected version before
reporting success. On macOS, the post-update check also verifies the LaunchAgent
is loaded/running for the active profile and the configured loopback port is
healthy. If the plist is installed but launchd is not supervising it, OpenClaw
re-bootstraps and kickstarts the LaunchAgent automatically, then reruns the
health/version/channel readiness checks. If the Gateway still does not become
healthy, the command exits non-zero and prints the restart log path plus explicit
restart, reinstall, and package rollback instructions. With `--no-restart`,
re-bootstraps the LaunchAgent automatically, then reruns the
health/version/channel readiness checks. A fresh bootstrap loads the RunAtLoad
job directly, so update recovery does not immediately `kickstart -k` the newly
spawned Gateway. If the Gateway still does not become healthy, the command exits
non-zero and prints the restart log path plus explicit restart, reinstall, and
package rollback instructions. With `--no-restart`,
package replacement still runs but the managed service is not stopped or
restarted, so the running Gateway may keep old code until you restart it
manually.