Skip to content

Add automated detection of when Execution API migration is missing #48887

@ashb

Description

@ashb

Body

Recently we merged #48650 which added a new field to the DagRun generated datamodel

Unfortunately since we have forbid extra in the generated client this resulted in old clients failing to work with new servers, one of the things we are deliberately using Cadwyn to avoid.

And it does help, when we remember/know to use it.

To prevent this happening again we should add automated testing of previous versions of the API spec.

We'll likely need to commit the "released" API version (which as of today is 2025-03-19 and 2025-09-26) and then see if any changes are made to them when re-generating against the code in a PR.

Or maybe we can look at using oasdiff/oasdiff to detect changes.

Regardless, we certainly need automated tooling to catch these errors.

Committer

  • I acknowledge that I am a maintainer/committer of the Apache Airflow project.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:APIAirflow's REST/HTTP APIarea:CIAirflow's tests and continious integrationarea:task-execution-interface-aip72AIP-72: Task Execution Interface (TEI) aka Task SDK

    Projects

    Status

    Icebox

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions