fix: verify backend rollout before publishing production OTA - #202
Merged
Merged
Conversation
4 tasks
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
1 participant
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.
Merging a backend-changing release previously started Railway deployment and production OTA independently, so phones could receive new code before the API was ready. Release publication now requires a manual run on main with the full commit verified on the API and workers; the guard rejects missing/mismatched revisions and a changed main head. The standalone OTA workflow publishes preview only.
Railway still auto-deploys main. This is an explicit operator confirmation, not an automated health probe: verify the deployments, health and release smoke checks before dispatch. Keep generation paused until compatible workers are confirmed. This prepares #200 for merge without publishing mobile code immediately.
Validation: all nine guard tests, shell syntax, YAML parsing and workflow wiring checks passed locally; a new CI job runs guard regressions. Application code is unchanged; prior app tests and exports remain applicable. Runbooks and backup status are updated. Preserve both focused commits. No production merge or deployment performed.