The GitHub Actions job "Tests" on airflow.git/re-introduce-use-migration-files has failed. Run started by GitHub user ephraimbuddy (triggered by ephraimbuddy).
Head commit for run: 86ed1f21188ac6a35efd086a3f8adea48ee43d04 / Ephraim Anierobi <[email protected]> Re-introducing `--use-migration-files` and fix inconsistences between ORM/migration files The `--use-migration-files` flag was removed in #41120 when we pruned the migration history for Airflow 3. At the time, we couldn't create a database from scratch using only migration files because the migration chain no longer started from an empty database. The oldest migration assumed an existing 2.6.2 schema. Now that we have a squashed migration (0000_2_6_2) with `down_revision = None` that creates the full baseline schema from scratch, we can re-introduce this flag. This enables a critical development workflow, which is: creating the database purely from migration files, then using `alembic revision --autogenerate` to detect schema drift between the ORM models and the migration-produced schema. Without this flag, `autogenerate` compares against an ORM-created database (via `create_all`), which masks any drift since both sides come from the same ORM definitions. Report URL: https://github.com/apache/airflow/actions/runs/22232961233 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
