fix(opencode-sms-bridge): select v1 route-prefix image - #215
Merged
Conversation
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
Select
ghcr.io/makeitworkcloud/opencode-sms-bridge:adb1e0e72729a7182b4a4929bd67e0275fba8173, the immutable image published after images PR #41. It corrects the OpenCode v1.18.23 session route prefix from the incompatible legacy V2/api/session...surface to the blocking HTTP-API/session...surface.Verified producer evidence: images buildah run 33976054695 passed and published the selected immutable tag at digest
sha256:607a426dad63dd563cfcca9f9720a0bc5068a8d812b4d4dabd63a0291895bd30.This PR changes only the bridge image tag in the existing
opencode-sms-bridgeApplication. It changes no chart version, Secret, routing/allowlist, Service, TunnelBinding, or sync policy.Fixes #
None — owner-authorized route-prefix repair rollout; no driving issue supplied.
Type of change
Validation
No local OpenTofu, SOPS, container build, cluster, or live-system operation was run or claimed.
Impact and rollout
Producer:
imagesmergedadb1e0e…and published the selected image. Publication is complete.Consumer:
workloads/apps/opencode-sms-bridge-app.yamlis the canonical GitOps image-selection point. This PR proposes, but does not itself perform, selection or reconciliation.Delivery stages: source is merged, published, and verified by producer CI; GitOps selection is proposed and PR validation is pending. An authorized merge runs
testonmain; only a successful test triggers automatic root-sync submission. Root and child reconciliation, resource health, Pod image, and the approved-source SMS reply remain separate verification stages.Rollback: use a reviewed GitOps PR to restore the prior immutable tag
6b48ddeaa5897a3d07dc28aa929a941219ec8993; do not retag images or patch live resources.Safety and secrets
AI-assisted change: an OpenCode agent materially produced this change; review the producer evidence, one-line diff, and automatic post-merge reconciliation behavior before merge.