Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix Git updater on stable channel checked out alpha tag instead of npm latest [2 pull requests]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…

During an OpenClaw update on a git-based install, openclaw update on the configured stable channel selected v2026.5.24-alpha.1 even though the stable/npm target reported by the tool was 2026.5.22.

Error Message

  1. node /opt/moltbot/openclaw.mjs update status reported npm/latest target 2026.5.22.
  2. openclaw update initially skipped because the working tree was dirty.
  3. After local changes were stashed/discarded, fetch hit stale local tags v2026.5.19 and v2026.5.19-beta.2.
  4. After deleting those stale local tags, openclaw update checked out v2026.5.24-alpha.1.
  5. openclaw update --tag v2026.5.22 still checked out the alpha tag; the option did not force the git checkout target in this git install.
  6. The gateway had not restarted yet, so production stayed on the previous healthy runtime until manual recovery.

Root Cause

  1. node /opt/moltbot/openclaw.mjs update status reported npm/latest target 2026.5.22.
  2. openclaw update initially skipped because the working tree was dirty.
  3. After local changes were stashed/discarded, fetch hit stale local tags v2026.5.19 and v2026.5.19-beta.2.
  4. After deleting those stale local tags, openclaw update checked out v2026.5.24-alpha.1.
  5. openclaw update --tag v2026.5.22 still checked out the alpha tag; the option did not force the git checkout target in this git install.
  6. The gateway had not restarted yet, so production stayed on the previous healthy runtime until manual recovery.

Fix Action

Fixed

Code Example

git -C /opt/moltbot checkout v2026.5.22
CI=true pnpm install --dir /opt/moltbot --frozen-lockfile
pnpm --dir /opt/moltbot run build
systemctl --user restart openclaw-gateway.service
RAW_BUFFERClick to expand / collapse

Summary

During an OpenClaw update on a git-based install, openclaw update on the configured stable channel selected v2026.5.24-alpha.1 even though the stable/npm target reported by the tool was 2026.5.22.

Environment

  • Install type: git
  • Install path: /opt/moltbot
  • Configured channel: stable
  • Starting version: 2026.5.18
  • Expected target: v2026.5.22
  • Unexpected checkout: v2026.5.24-alpha.1
  • Final recovered state: CLI and gateway 2026.5.22, git tag v2026.5.22, commit a374c3a5bfd

Observed behavior

  1. node /opt/moltbot/openclaw.mjs update status reported npm/latest target 2026.5.22.
  2. openclaw update initially skipped because the working tree was dirty.
  3. After local changes were stashed/discarded, fetch hit stale local tags v2026.5.19 and v2026.5.19-beta.2.
  4. After deleting those stale local tags, openclaw update checked out v2026.5.24-alpha.1.
  5. openclaw update --tag v2026.5.22 still checked out the alpha tag; the option did not force the git checkout target in this git install.
  6. The gateway had not restarted yet, so production stayed on the previous healthy runtime until manual recovery.

Expected behavior

For a git-based install on channel stable, openclaw update should follow the stable/npm latest target, or at minimum refuse if the resolved git tag is prerelease (alpha/beta) while the configured channel is stable.

Recovery applied

The update was completed manually because the official update path was selecting the wrong tag:

git -C /opt/moltbot checkout v2026.5.22
CI=true pnpm install --dir /opt/moltbot --frozen-lockfile
pnpm --dir /opt/moltbot run build
systemctl --user restart openclaw-gateway.service

Verification after recovery

  • node /opt/moltbot/openclaw.mjs --version -> OpenClaw 2026.5.22 (a374c3a)
  • node /opt/moltbot/openclaw.mjs gateway status -> CLI and gateway 2026.5.22, connectivity probe OK
  • node /opt/moltbot/openclaw.mjs update status -> git HEAD · npm latest 2026.5.22 · deps ok

Notes

Local guardrails were added on our side to stop future updates if git stable resolves to alpha, beta, or a version different from npm latest.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

FAQ

Expected behavior

For a git-based install on channel stable, openclaw update should follow the stable/npm latest target, or at minimum refuse if the resolved git tag is prerelease (alpha/beta) while the configured channel is stable.

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - 💡(How to fix) Fix Git updater on stable channel checked out alpha tag instead of npm latest [2 pull requests]