fix(release): preserve beta validation evidence#103796
Merged
Merged
Conversation
vincentkoc
marked this pull request as ready for review
July 10, 2026 15:56
Member
Author
|
Merged via squash.
|
github-actions Bot
pushed a commit
to Desicool/openclaw
that referenced
this pull request
Jul 11, 2026
* fix(release): proxy upgrade fixtures to npm (cherry picked from commit 30f54a5) * fix(release): require installer doctor evidence (cherry picked from commit 0782a94) * test(qa): scope aborted restart outcome to Codex (cherry picked from commit ac54f80) --------- Co-authored-by: Peter Steinberger <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What Problem This Solves
Fixes three release-validation gaps that can hide a broken beta candidate:
Why This Change Was Made
This forward-ports three signed, release-proven fixes without changing product runtime behavior. The upgrade fixture proxies public package misses to npm, installer smoke validates the required doctor step while retaining the documented advisory exit, and the QA assertion is scoped to the Codex runtime.
User Impact
Release operators get reliable failure signals from configured-plugin upgrades, installer doctor verification, and OpenClaw/Codex restart parity. There is no end-user runtime change.
Evidence
-xforward-ports of release commits30f54a5fe1e,0782a94452d, andac54f80430c; stable patch IDs area036959f9501,5c90c03797a0, and1115e92a4f15.db39fe807202plus the exact seven-path patch produced treeaca775269f72, identical to local headee55a602c4dd.tbx_01kx696v225r2c77w5spxwq73q: final-tree focused proof passed273/273(164Docker helper,71installer,38QA catalog).gateway-restart-inflight-runpassed with--runtime-pair openclaw,codex --provider-mode mock-openai.check:changedpassed all-project tsgo, core/extensions/scripts lint, guards, and import-cycle checks. Subsequent base commits did not overlap the seven paths.[email protected]configured-plugin upgrade survivor passed candidate packaging, doctor, gateway health/readiness, and status probes.0.86.Changelog is not required for validation-only tooling.
AI-assisted; maintainer-reviewed source, scenario, and exact-tree evidence are included above.