Skip to content

Test airflowctl with prior core versions from main #57826

Open
Task
Open
Test airflowctl with prior core versions from main#57826
Task
Assignees
Andrushika
Labels
area:CIAirflow's tests and continious integrationarea:airflow-ctlkind:featureFeature Requests

Description

@bugraoz93
bugraoz93
opened on Nov 4, 2025

Description

We need to run airflowctl integration tests for the latest stable build images from the v3-1 branch and the main branch simultaneously in the main scheduled pipelines.

Use case/motivation

Currently, integration tests are running with their current version in the same pipeline. That means, for example, releasing the current version of airflowctl from main while ensuring that the code is compatible with 3.1 as well.

Related issues

No response

Are you willing to submit a PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Activity

  1. bugraoz93
    self-assigned this
    on Nov 4, 2025
  2. bugraoz93
    added
    kind:featureFeature Requests
    on Nov 4, 2025
  3. bugraoz93
    added the
    Task
    issue type on Nov 4, 2025
  4. bugraoz93
    added
    area:CIAirflow's tests and continious integration
    area:airflow-ctl
    on Nov 4, 2025

  5. Andrushika commented on Oct 25, 2026

    @Andrushika
    Andrushika
    on Oct 25, 2026
    Contributor

    According to the recent discussion about airflowctl 0.1.6 release on dev@: https://lists.apache.org/thread/7ocgsn7lzxnnbmfopyt6ko5wvkrm7rcn

    I ran the existing airflowctl integration tests from airflow-ctl/v0-1-test (what becomes 0.1.6) against the released images apache/airflow:3.2.2, 3.3.2 and 3.4.0b2. Each run has 151 tests. What I found:

    • 3.4.0b2: assets list and assets get fail with extra_forbidden on team_name.
      UI: Show owning team in asset dependency popovers #71446 added this field to asset reference models that use StrictBaseModel, so the branch's generated models reject it. Main already has the field, so only the release branch is affected.
    • 3.2.2: the six assets *-state-store commands get 404/405, because that API only exists from 3.3. The tests would need version-gating for a 3.2 cell.
    • All three: the xcom and dagrun delete steps after dags trigger are flaky. The test writes an XCom before the task starts, and the task clears its XComs when it starts. This is not version related.

    I will open PRs fixing these problems soon! Hope we can get airflowctl released shortly.

    cc @shahar1

  6. shahar1
    assigned
    Andrushika
    and unassigned
    bugraoz93
    on Oct 25, 2026

  7. shahar1 commented on Oct 25, 2026

    @shahar1
    shahar1
    on Oct 25, 2026
    Contributor

    According to the recent discussion about airflowctl 0.1.6 release on dev@: https://lists.apache.org/thread/7ocgsn7lzxnnbmfopyt6ko5wvkrm7rcn

    I ran the existing airflowctl integration tests from airflow-ctl/v0-1-test (what becomes 0.1.6) against the released images apache/airflow:3.2.2, 3.3.2 and 3.4.0b2. Each run has 151 tests. What I found:

    • 3.4.0b2: assets list and assets get fail with extra_forbidden on team_name.
      UI: Show owning team in asset dependency popovers #71446 added this field to asset reference models that use StrictBaseModel, so the branch's generated models reject it. Main already has the field, so only the release branch is affected.
    • 3.2.2: the six assets *-state-store commands get 404/405, because that API only exists from 3.3. The tests would need version-gating for a 3.2 cell.
    • All three: the xcom and dagrun delete steps after dags trigger are flaky. The test writes an XCom before the task starts, and the task clears its XComs when it starts. This is not version related.

    I will open PRs fixing these problems soon! Hope we can get airflowctl released shortly.

    cc @shahar1

    Thanks! It would be great :)

  8. Andrushika commented on Oct 27, 2026

    @Andrushika
    Andrushika
    on Oct 27, 2026
    Contributor

    Hi @shahar1 I think we'll need to backport #67065, #72260 and #75610 to fix the release branch.
    Do you mind if I prepare these cherry-picks and open PRs myself? Or do you prefer to do it from your side?
    I can help if you are busy :) (but will need your review and approval)

  9. shahar1 commented on Oct 27, 2026

    @shahar1
    shahar1
    on Oct 27, 2026
    Contributor

    10. Hi @shahar1 I think we'll need to backport #67065, #72260 and #75610 to fix the release branch.
    Do you mind if I prepare these cherry-picks and open PRs myself? Or do you prefer to do it from your side?
    I can help if you are busy :) (but will need your review and approval)

    @Andrushika Go ahead, thank you!

  10. Andrushika commented on Oct 27, 2026

    @Andrushika
    Andrushika
    on Oct 27, 2026
    Contributor

    Thanks Shahar! I just created some PRs.

    Cherry-picks:

    Test fix for servers older than 3.3: #75753

    I opened them all at once, so the time difference won't slow down our review process. Hopefully that doesn't look like spam...
    Please take a look when you have a chance, really appreciate it!!

    I will work on more after some of these get merged. I'm hitting the open PR limit at the moment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area:CIAirflow's tests and continious integrationarea:airflow-ctlkind:featureFeature Requests

Type

Task

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions