chore(openclaw): bump dev/prod tag to extended image 2026.4.22-dbf5da0#416
Merged
Conversation
Build workflow on PR #415 pushed 877352799272.dkr.ecr.us-east-1.amazonaws.com/isol8/openclaw-extended:2026.4.22-dbf5da0 to ECR (digest sha256:b75fd3a0). Switching dev+prod off the unresolvable -bootstrap placeholder. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
5 tasks
prez2307
added a commit
that referenced
this pull request
Apr 29, 2026
… actual rollback (#418) PR #415 + #416 only updated openclaw-version.json but the extended Dockerfile keeps a hardcoded `FROM alpine/openclaw:2026.4.25-slim` (line 63). The build workflow tags the resulting image as 2026.4.22-<sha> — but it was always built FROM 4.25-slim. So every "rollback test" was still on the broken 4.25-slim base, with all of #73517's NFS+SQLite hang behavior intact. Same hang every time, just labeled differently. The Dockerfile's own header comment (lines 12-13) literally says: "Bump UPSTREAM = openclaw-version.json#upstream field. Keep the FROM lines below in sync with that field manually until automation lands." — the manual sync was missed. Fix: change line 63 to FROM alpine/openclaw:2026.4.22 (the fat upstream tag, which exists on Docker Hub, last_updated 2026-04-23, 1.2 GB). Once this PR merges, build-openclaw-image.yml will produce a new ECR tag 2026.4.22-<sha> built FROM the actual 4.22 base. A follow-up bump of openclaw-version.json#dev.tag/prod.tag will deploy it. Includes the openclaw-version.json from origin/main HEAD (b590890) so the diff is purely the Dockerfile FROM line. TODO follow-up: parameterize the FROM line via build-arg so this can't drift from openclaw-version.json again. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Follow-up to #415. The build workflow on the merge of #415 pushed
877352799272.dkr.ecr.us-east-1.amazonaws.com/isol8/openclaw-extended:2026.4.22-dbf5da0to ECR (digestsha256:b75fd3a0...). Switchesdev.tagandprod.tagoff the unresolvable-bootstrapplaceholder.Test plan
[gateway] readyand stays responsive paststarting channels and sidecars...[ws] closed before connect code=1006storm in gateway logs🤖 Generated with Claude Code