Andrushika opened a new pull request, #75753: URL: https://github.com/apache/airflow/pull/75753
## Why The airflowctl integration tests start Airflow with Docker Compose and run each airflowctl command against it. The `DOCKER_IMAGE` variable selects the Airflow image. So the same tests can run against an older Airflow (#57826). The asset and task instance state store APIs first shipped in Airflow 3.3.0. Against `apache/airflow:3.2.2`, all 13 state store commands fail with 404 or 405. Each command runs in two login modes. This gives 26 failures, and none of them is a compatibility bug. The CI of `airflow-ctl/v0-1-test` runs against Airflow 3.2.1. To unblock that CI, #70724 skips the asset state store tests for every server. So these commands have no integration coverage, even against a 3.3 server. ## What A session fixture reads the server version from `/api/v2/version`. `MIN_AIRFLOW_VERSIONS` gives the first Airflow version for each state store command. If the server is older, the test skips. CI on main uses a server that has these APIs, so CI never runs the skip. A new test checks that each key in `MIN_AIRFLOW_VERSIONS` still matches a command in `TEST_COMMANDS`. If a command gets a new name and the table does not, this test fails. I ran the suite locally before and after this change: - 3.2.2: the 26 state store tests skip. All other results are the same as before. - 3.3.2: the 26 state store tests run and pass. On main, the 3.2.2 run needs `psycopg2` in the Compose connection URLs. The 3.2.2 image does not include `psycopg` (#69469). I changed this only for the local run. After this merges, I plan to backport it to `airflow-ctl/v0-1-test` in place of the skip from #70724. related: #57826 --- ##### Was generative AI tooling used to co-author this PR? - [x] Yes (please specify the tool below) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
