Check failed-migration schema version against its prior value
Foundation / checks (checks) (push) Successful in 5s
Foundation / checks (client) (push) Successful in 5s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 4s
Foundation / checks (deploy) (push) Successful in 3m28s
Foundation / checks (postgres) (push) Failing after 40m43s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

The upgrade rehearsal asserted the schema stayed at version 23 after a
deliberately failing migration, but migrations now reach 33, so it
reported "schema version moved" although nothing changed. Record the
version before the failing migration and compare against that. Refresh
the dev session window.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-12 16:28:57 -04:00
co-authored by Claude Opus 5.5
parent fcccdf552f
commit bf5dcc7a6e
2 changed files with 4 additions and 2 deletions
@@ -12,7 +12,7 @@ spec:
env:
- {name: REGION_SESSION, value: "dev"}
- {name: REGION_SESSION_LISTEN, value: "0.0.0.0:7400"}
- {name: REGION_SESSION_WINDOW, value: "dev-20261012T194122-12341:1791835282"}
- {name: REGION_SESSION_WINDOW, value: "dev-20261012T202838-20650:1791838118"}
- {name: REGION_M10_MAX_GRANT_LIFETIME, value: "14400"}
ports:
# QUIC (ADR-0090): UDP only; nothing listens on TCP 7400.