Remove the retired Roomote-Ops fleet dispatch - #978
Merged
Conversation
Roomote-Ops was archived on 2026-08-01: every production tenant is Cloud-managed, and this dispatch had been resurrecting the quiesced legacy Railway projects' write paths on every main build — stale twins of migrated tenants consuming inbound work against frozen databases. The ROOMOTE_OPS_REPO variable was already deleted (which disabled the job); this removes the dead job itself. Cloud image rollouts are unaffected — they run through notify-production-cloud/notify-staging- cloud against Roomote-Cloud.
Contributor
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.
Companion cleanup to archiving Roomote-Ops (2026-08-01).
Every production tenant is Cloud-managed as of the migrations completing, and this dispatch had a live failure mode: it deployed to the
railway-*environments on every main build, resurrecting the quiesced legacy projects' write paths — stale twins of migrated tenants consuming Telegram polls and queued jobs against frozen databases. The kill switch (deleting theROOMOTE_OPS_REPOvariable) is already thrown and the seven deploy environments are deleted; this PR removes the deadnotify-opsjob and updates the neighbouring comment.Cloud rollouts are untouched — staging/production image delivery goes through the Roomote-Cloud dispatches, which share the
roomote-main-buildevent name but different repos/secrets.Also done outside this PR: the orphaned
ROOMOTE_OPS_DISPATCH_TOKENrepo secret is being removed; if the underlying PAT was single-purpose it can be revoked in GitHub settings.