Deprecate SMS bridge image publication - #50
Merged
Merged
Conversation
… publication Filter opencode-sms-bridge out of every Makefile selection target (changed-images, list-images, list-images-json) so automatic matrix detection can never select it for build, push, or attestation. Reject a manual workflow_dispatch image input that names a retired or unknown directory by validating it against make list-images-json, failing the detect job before the build and attest jobs run. Add a deprecation notice to the image README. Source, Containerfile, and tests are retained; existing GHCR tags and attestations are untouched.
Image CI passedPre-commit validation passed. View the workflow run. |
8 tasks
xnoto
added a commit
that referenced
this pull request
Sep 20, 2026
## Summary Complete owner-approved deletion of retired Twilio/SMS image source with no archive. Remove the bridge Containerfile, server implementation, tests and README. Remove only the now-redundant retired-image filter; generic discovery and manual-input whitelist remain intact. Fixes: N/A — full retirement request; follows #50 and verified cluster/provider cleanup. ## Type of change - [x] Container image - [x] Refactor / cleanup - [x] Breaking change ## Validation - [ ] Required PR checks pass — pending. - [x] No generated files hand-edited. Independent adversarial/security ADVANCE at7e3aa214deac847d57c266f77336cd68f661b503. Existing checks and autodiscovery should exclude the removed source and produce no retired image. No local tests or image publication claimed. ## Impact and rollout Runtime bridge and provider resources already removed; no live consumer remains. Main deletion should select no image builds for this path. Other image sources/workflows remain unchanged. Historical GHCR packages are not deleted by this source change and require a separate supported removal operation. No archive copy; Git history is not rewritten. ## Safety and secrets - [x] No credentials, decrypted values, state, or sensitive plans - [x] No local OpenTofu operations - [x] Source removal and package boundary described above AI-assisted; owner approved full removal; no upstream communications.
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
Owner-approved SMS/Twilio retirement preparation. Exclude
opencode-sms-bridgefrom automatic/all-image selection and reject retired or unknown explicit workflow inputs. Preserve source, existing GHCR tags, and attestations. No upstream communications.Fixes: N/A — owner request.
Type of change
Validation
Independent adversarial and infrastructure-security reviews found no remaining Critical/High issue. No local checks or workflow dispatch performed. CI must validate selection/hygiene; account or live delivery was not tested.
Impact and rollout
Producer: images build selection. Consumer: existing SMS bridge chart remains pinned separately; no running resources or historic artifacts removed. Merge stops future publication of this image, but does not stop its deployment. Discord activation and bridge retirement are separate confirmation-gated changes. Existing image remains usable for rollback. No package deletion, phone release, or account teardown.
Safety and secrets
AI-assisted change. Do not merge without explicit owner confirmation.