revert(items): restore openclaw 2026.7.1 pin, probe and bind - #5
Merged
Conversation
This reverts commit 8735910 (PR #3). That change bumped the item to 2026.8.1 and rewrote the component's runtime contract with it: readiness moved from /readyz to /startupz, the gateway exec gained --bind lan --port 18789, and seven container-side paths were pinned as envVars. None of it was exercised against a running image -- the devcontainer has no container runtime, so every behavioural claim in the change rests on upstream documentation alone. The deciding item is the upgrade path. 2026.8.1 carries two breaking migrations (OpenProse plugin removal, codex/* -> openai/* model refs), and existing deployments cross them in place against volumes already holding user config and session history. A startup migration that cannot repair safely exits rather than reporting healthy, and upstream's recovery is a manual `doctor --fix` run against the same mounts -- which a user deploying from this catalog has no obvious way to invoke. Both files return byte-for-byte to their pre-#3 state; no other item is touched. The analysis in #3 stands and is worth re-landing once it can be verified on a host with Docker -- tracked in the issue this reverts under. Verified: typecheck clean, item suite 25/25, full corpus 377/377, and the working tree for items/openclaw is identical to 8735910^. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016tsLtVNyw9oU8YgBwzxu6M
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
1 participant
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.
Reverts #3 in full, restoring the OpenClaw item to
ghcr.io/openclaw/openclaw:2026.7.1.Closes #4.
Why
#3 bumped the item to
2026.8.1and rewrote the component's admission path with it — readiness/readyz→/startupz,--bind lan --port 18789on the gateway exec, seven container-side paths pinned asenvVars. Its own "Not verified" section then listed what never ran, because the devcontainer has no container runtime:2026.8.1, including whetherconfig setstill exits 02026.7.1→2026.8.1in-place upgrade on a shared volume, across two breaking migrations (OpenProse plugin removal,codex/*→openai/*model refs)The upgrade path is the deciding one. Existing deployments cross those migrations in place against volumes already holding user config, session history, and the OAuth-token encryption key. Upstream's stated behaviour is that a startup migration which cannot repair safely exits rather than reporting healthy, with recovery being a manual
doctor --fixagainst the same mounts — not something a user deploying from this catalog can invoke. The probe and bind changes may well be correct, but they were merged on documentation alone and they sit directly between the platform edge and a deployment being marked healthy.Full reasoning and re-land criteria in #4. The analysis in #3 is sound and stands on the record for a re-land once it can be exercised on a host with Docker.
Diff
Mechanical
git revertof8735910, applied clean with no conflicts.items/openclaw/components/openclaw.yamlenvVars, volume commentitems/openclaw/listing.yamlBoth files are byte-for-byte identical to their pre-#3 state —
git diff 8735910^ -- items/openclaw/is empty. No other item is touched.Verified
npm run typecheckcleantask test:item -- openclaw25/25items/openclawconfirmed identical to8735910^Nothing here needs a container runtime: this restores a state that was previously live-verified rather than asserting anything new about a running image.
🤖 Generated with Claude Code
https://claude.ai/code/session_016tsLtVNyw9oU8YgBwzxu6M