Grapevine release completed
The tested digest passed the guarded production rollout, container health checks, and the public readiness check. No rollback was needed.
Live-ish service status, plus whatever we need you to know.
Repos, pushes, and pulls are doing their thing.
Grapevine is healthy on the newly promoted release.
Member profiles are available.
Authentication is available and healthy.
The tested digest passed the guarded production rollout, container health checks, and the public readiness check. No rollback was needed.
The tested beta is being promoted through the guarded production rollout. Health and readiness checks must pass before it remains live.
The corrected Grapevine release passed beta acceptance and the guarded production rollout completed without rollback. Chat, login, and member profiles are operational.
The guarded retry failed Grapevine production container-health and readiness checks, so it rolled back again. The previous stable release is serving traffic while the environment-specific failure is investigated.
The prior attempt rolled back cleanly after the stale readiness gate expired. The bounded readiness fix is installed and the same accepted release is being retried under the guarded deploy.
The corrected candidate failed the guarded production health gate, so deployment was automatically rolled back. Services are healthy on the previous stable release while the gate is investigated.
The corrected beta release passed testing and is now being rolled out under the guarded production deploy. Chat, profiles, and login may briefly be interrupted; updates will appear here.
The new release failed production health checks and was automatically rolled back. Services are operating on the previous stable release while the candidate is investigated.
The tested beta release is being rolled out. Chat, profiles, and login may briefly be interrupted; updates will appear here.