#Rolled back to 2026.4.22

1 messages · Page 1 of 1 (latest)

timber badge
#

I often upgrade to the latest version early, however, .23 had some new ACP issues for me and .24 killed my Raspberry Pi with kernel watchdog reboots due to bug #72270. So I rolled back to .22 as this is the last good copy for me. I noticed that the WebUI is asking if I want to upgrade to to .23, and not .24, and this made me think. When I do upgrade from .22, do I need to hop through the intermediate versions or can I upgrade direct to the latest?

raw trailBOT
#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

gusty plinthBOT
#

Short answer: you can upgrade direct to the latest; no need to hop through .23 first.

openclaw update resolves your current channel target, fetches that version, runs doctor, and restarts the gateway. Stable maps to npm latest; the docs also recommend openclaw update --dry-run to preview the target before applying. (docs.openclaw.ai)

For your case I’d do:

openclaw update status
openclaw update --dry-run

If it shows a version you trust, then:

openclaw update