Issue Station
Sign In
Tools hereToolbox

openclaw - 💡(How to fix) Fix fix: beta package upgrades can fail during legacy updater handoff [1 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…

The beta4-to-beta5 package upgrade path exposed a legacy updater handoff problem. Older package update parents run a newer candidate openclaw doctor --fix during the package swap, then resume in the old process and run their own stale post-core logic. That mixed-process flow hit multiple failures while validating the beta5 candidate.

Error Message

  • ClawHub artifact-download unavailability should be a structured, fallback-safe error for doctor/onboarding, while integrity and security mismatches remain fail-closed.

Root Cause

  1. [email protected] launched the candidate doctor during upgrade.
  2. The candidate doctor wrote config metadata with the candidate/current OpenClaw version.
  3. The beta4 parent resumed and rejected the config because it appeared to have been written by a newer OpenClaw.
  4. After avoiding the future config stamp, the beta4 parent still resumed into stale post-core plugin convergence.
  5. That stale convergence tried to install Matrix from clawhub:@openclaw/matrix@beta and failed when the ClawHub artifact was unavailable instead of using the current npm fallback behavior.

Fix Action

Fixed

RAW_BUFFERClick to expand / collapse

Summary

The beta4-to-beta5 package upgrade path exposed a legacy updater handoff problem. Older package update parents run a newer candidate openclaw doctor --fix during the package swap, then resume in the old process and run their own stale post-core logic. That mixed-process flow hit multiple failures while validating the beta5 candidate.

What we saw

  1. [email protected] launched the candidate doctor during upgrade.
  2. The candidate doctor wrote config metadata with the candidate/current OpenClaw version.
  3. The beta4 parent resumed and rejected the config because it appeared to have been written by a newer OpenClaw.
  4. After avoiding the future config stamp, the beta4 parent still resumed into stale post-core plugin convergence.
  5. That stale convergence tried to install Matrix from clawhub:@openclaw/matrix@beta and failed when the ClawHub artifact was unavailable instead of using the current npm fallback behavior.

Desired behavior

  • Current update parents should continue to defer package-manager plugin repair to the updated post-core convergence pass.
  • Legacy update parents should allow the candidate doctor to repair configured plugin installs before the old parent resumes.
  • Candidate doctor should not write config metadata that an old parent will reject when it resumes.
  • ClawHub artifact-download unavailability should be a structured, fallback-safe error for doctor/onboarding, while integrity and security mismatches remain fail-closed.

Proof trail

Fix path

PR #83350 updates the legacy package-update handoff so the candidate doctor can safely handle the repair path without leaving a future-stamped config behind for the old parent.

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…
#api#ssr#installation#API versioning#request timeout

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 fix: beta package upgrades can fail during legacy updater handoff [1 pull requests]