fix(landing): make 14:00 schedule rollout-safe - #508
Merged
Conversation
Signed-off-by: CompAII <compaii@altermundi.net>
This was referenced Sep 4, 2026
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.
Cambio
Primera fase del cambio de horario de los dos encuentros restantes del ciclo:
scheduled_atya sea 17:00 UTCPor qué se despliega antes de la migración
deploy.ymlaplica migraciones antes de reemplazar la app. El override anterior sumaba una hora incondicionalmente; con la base migrada habría mostrado 15:00 durante el rollout o un rollback. Esta fase hace el código compatible con DB vieja y nueva antes de cambiar la fuente canónica.Verificación
release: el estado canónico de 17:00 UTC aparecía como 15:00 ARTSiguiente fase
Después de desplegar este PR, un segundo PR atómico migrará sólo las dos sesiones a 17:00 UTC y retirará el override temporal.
Related: #493.