Repository navigation
chore(admins-openclaw): bump image to 2026.4.28-beta.1 (canary) - #53
Conversation
|
@codex review |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: fa2313336e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| image: | ||
| repository: ghcr.io/mctlhq/mctl-openclaw | ||
| tag: "2026.4.26-beta.1" | ||
| tag: "2026.4.28-beta.1" |
There was a problem hiding this comment.
This bump changes the deployed image to 2026.4.28-beta.1, but the OPENCLAW_VERSION env var in the same values file is still 2026.4.26-beta.1. In canary validation and incident debugging, this creates a version skew where runtime-reported version metadata no longer matches the actual binary, which can mislead health checks, dashboards, and rollback decisions tied to reported version strings.
Useful? React with 👍 / 👎.
Codex P2 on #53: image tag was bumped to 2026.4.28-beta.1 but the runtime-reported OPENCLAW_VERSION env stayed at 2026.4.26-beta.1. Keeping them in sync prevents misleading dashboard/health-check output during canary validation and rollback decisions.
|
Codex Review: Didn't find any major issues. Swish! ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Summary
admins/openclawimage tag from2026.4.26-beta.1→2026.4.28-beta.1openclaw/openclaw:main2026-04-23 sync via mctl-openclaw PRs deploy: libertex/nginx → latest (Docker Hub) #8 (bare upstream merge) + Consolidate deploy-worker into deploy-service template #9 (fork-side fixups)Risk
dc2c3a4920"harden WS pairing locality") and other auth/protocol changespnpm check(exit 0) and a new unit-test suite for the trusted-proxy role propagationTest plan
admins-openclawcleanly (Synced, Healthy)sha256:5d5cac92..., arm64sha256:25f93fd0...)out of extra usage/ missing.claude.jsonregressions