Repository navigation
chore(mctl-agent): bump image to 1.7.0 (rollback resolver) - #105
Merged
Merged
Conversation
mctl-agent 1.7.0 closes the post-deploy rollback path: when a pod crash-loops within 30 min of a deploy, the agent now resolves the previous image tag from the gitops history of the service's values.yaml and opens a rollback PR (AutoMergeSafe=false; human clicks /approve in Telegram). Combined with the global telegram fallback flip in PR #99, openclaw- admins (and platform-wide) crashes now reach the admins-openclaw chat with both diagnosis and a one-click rollback handle. Known limitations documented in internal/fixer/previous_tag.go godoc: empty-quoted tags + multi-image-block fallback. Both are theoretical shapes that don't exist in mctl-gitops today; revisit when a real values file regresses.
Member
Author
|
@codex review |
Member
Author
|
@copilot review |
Review of commit d906880 The change is a clean, minimal single-line YAML bump: What looks good:
One pre-merge risk to keep in mind (already flagged in the PR description):
No code issues found — the change is correct and safe to merge once the image is confirmed published. |
|
Codex Review: Didn't find any major issues. Breezy! ℹ️ 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". |
This was referenced May 3, 2026
This was referenced Aug 4, 2026
This was referenced Aug 28, 2026
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.
Summary
Bump admins/mctl-agent image from
1.6.0to1.7.0.1.7.0ships the post-deploy rollback path that was previously diagnose-only —internal/pipeline/pipeline.go:381-382no longer errors out with "rollback requires previous tag — not yet implemented". On a pod crash-loop within 30 min of a deploy, mctl-agent now:image.tagfrom the gitops history of the service's values.yaml,/approve//rejecthandles.Combined with the admins-fallback Telegram flip in #99, openclaw-admins (and platform) crashes now land with operators in the admins-openclaw chat.
Wait for image build
Tag
1.7.0was pushed at 2026-05-03T07:09Z; image build is in flight on mctl-agent. Do not merge untilghcr.io/mctlhq/mctl-agent:1.7.0is published, otherwise the pod will sit inImagePullBackOff.Test plan
gh run list --repo mctlhq/mctl-agent --limit 1shows the1.7.0build at conclusion=successkubectl -n admins rollout status deploy/admins-mctl-agent-base-serviceis healthykubectl -n admins describe pod -l app.kubernetes.io/instance=admins-mctl-agent | grep Image:resolves toghcr.io/mctlhq/mctl-agent:1.7.0