Hi Team,We’ve successfully provisioned a test environment on GCP (Compute Engine + Cloud SQL) and validated the infrastructure. While networking, IAP, and Nginx are all green ($/healthz$ returns 200), we are hitting a wall with the database migration.
Current Status:
Infrastructure: Verified. Networking and permissions are correct.
Stable Version: The app runs healthily on v1.13.7 with our imported production DB dump.
The Issue: When upgrading to latest or v1.16.4, the app fails due to schema mismatches.
Error Logs: We're seeing missing relations and columns, specifically relation "core.cronTrigger" does not exist and column ... standardId does not exist.
The Diagnosis: The UI reports "Unable to Reach Back-end" because the app logic fails on these missing elements, even though the transport layer is functional. It appears we cannot jump directly from v1.13.x to v1.16.x with our current data dump.
Our Plan: We are looking to implement a stepwise minor version upgrade path. Are there specific "stop-gap" versions or migration scripts we should prioritize to bridge the gap between v1.13.7 and the current release?