Skip to content

fix(openclaw): pin to 2026.4.22 (latest fat stable, no beta)#406

Merged
prez2307 merged 1 commit into
mainfrom
fix/openclaw-stable-tag
Apr 28, 2026
Merged

fix(openclaw): pin to 2026.4.22 (latest fat stable, no beta)#406
prez2307 merged 1 commit into
mainfrom
fix/openclaw-stable-tag

Conversation

@prez2307
Copy link
Copy Markdown
Contributor

Summary

Stepping back from 2026.4.25-beta.11 (PR #405) to the most recent fat stable tag: alpine/openclaw:2026.4.22 (2026-04-23).

Why

Upstream stopped publishing fat variants for .23/.24/.25 stables — only -slim and -beta.X are available for those. 2026.4.22 is the latest tag matching ^\d{4}\.\d+\.\d+$ on Docker Hub.

Still well past the v2026.4.7 minimum required for CODEX_HOME + pre-staged auth.json (commit 7e0e2f81e5), so the codex-auth flow we just shipped in PR #404 still works.

Test plan

  • build-openclaw-image succeeds with alpine/openclaw:2026.4.22
  • Follow-up PR bumps dev.tag / prod.tag to the actual 2026.4.22-<sha> once it lands in ECR

🤖 Generated with Claude Code

Stepping back from 2026.4.25-beta.11 to the most recent fat (non-slim,
non-beta) stable tag published by upstream: alpine/openclaw:2026.4.22
(2026-04-23). Still well past the v2026.4.7 minimum required for the
CODEX_HOME / pre-staged auth.json feature added in commit 7e0e2f81e5.

Verified via Docker Hub API: 2026.4.22 is the most recent matching
^\d{4}\.\d+\.\d+$ tag. Upstream stopped publishing fat variants for
.23/.24/.25 stables — only -slim and -beta.X variants for those.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@prez2307 prez2307 merged commit 8f7d43e into main Apr 28, 2026
@prez2307 prez2307 deleted the fix/openclaw-stable-tag branch April 28, 2026 03:16
prez2307 added a commit that referenced this pull request Apr 29, 2026
v2026.4.25-slim wedges every container start: gateway main thread enters
uninterruptible NFS RPC wait (rpc_wait_bit_killable) on
~/.openclaw/tasks/runs.sqlite via OpenClaw's loopback-NFS layer
(127.0.0.1:21005). Matches upstream issue #73517 ("Gateway task registry
maintenance can hot-loop on stale runs.sqlite"), reproduced against
2026.4.25 (aa36ee6). v2026.4.26 partially fixes the WAL growth side
(#72774) but introduces an unfixed acpx EPERM regression on remote FS
(#73333), so we can't move forward — only back.

2026.4.22 fat predates #73517, has CODEX_HOME (added 4.7) so ChatGPT
OAuth still works, and bundles all plugin runtime deps in-image so
first boot doesn't pay the 90s slim install penalty. We previously
ran on 4.22 fat in PR #406 without this hang.

Schema-compliance changes (zod-schema.agent-defaults.ts at v2026.4.22
requires these three fields, no .optional()):
- agents.defaults.embeddedHarness: {} (line 42)
- agents.defaults.contextLimits: {}  (line 115)
- agents.defaults.heartbeat: {}      (line 251)

Also reverts the channel-disable defensive patch from #413: the no-account
enabled:true channel-plugin behavior was a v4.25 sidecar bug, not a 4.22
issue. Channels are back to enabled:true so first-pair stays a fast
hot-reload instead of a 6-min full gateway restart on Fargate.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
prez2307 added a commit that referenced this pull request Apr 29, 2026
…ang (#415)

v2026.4.25-slim wedges every container start: gateway main thread enters
uninterruptible NFS RPC wait (rpc_wait_bit_killable) on
~/.openclaw/tasks/runs.sqlite via OpenClaw's loopback-NFS layer
(127.0.0.1:21005). Matches upstream issue #73517 ("Gateway task registry
maintenance can hot-loop on stale runs.sqlite"), reproduced against
2026.4.25 (aa36ee6). v2026.4.26 partially fixes the WAL growth side
(#72774) but introduces an unfixed acpx EPERM regression on remote FS
(#73333), so we can't move forward — only back.

2026.4.22 fat predates #73517, has CODEX_HOME (added 4.7) so ChatGPT
OAuth still works, and bundles all plugin runtime deps in-image so
first boot doesn't pay the 90s slim install penalty. We previously
ran on 4.22 fat in PR #406 without this hang.

Schema-compliance changes (zod-schema.agent-defaults.ts at v2026.4.22
requires these three fields, no .optional()):
- agents.defaults.embeddedHarness: {} (line 42)
- agents.defaults.contextLimits: {}  (line 115)
- agents.defaults.heartbeat: {}      (line 251)

Also reverts the channel-disable defensive patch from #413: the no-account
enabled:true channel-plugin behavior was a v4.25 sidecar bug, not a 4.22
issue. Channels are back to enabled:true so first-pair stays a fast
hot-reload instead of a 6-min full gateway restart on Fargate.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant