Skip to content

Conversation

@vincbeck
Copy link
Contributor

This PR should resolve test failures we see in main in api_connexion.


^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

@boring-cyborg boring-cyborg bot added the area:API Airflow's REST/HTTP API label Jan 29, 2025
@vincbeck vincbeck added the legacy api Whether legacy API changes should be allowed in PR label Jan 29, 2025
@vincbeck vincbeck closed this Jan 29, 2025
@vincbeck vincbeck reopened this Jan 29, 2025
Copy link
Contributor

@amoghrajesh amoghrajesh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh!!! LGTM

@vincbeck vincbeck merged commit 41403c1 into apache:main Jan 29, 2025
85 of 88 checks passed
@vincbeck vincbeck deleted the vincbeck/fix_main_api_connexion branch January 29, 2025 16:17
got686-yandex pushed a commit to got686-yandex/airflow that referenced this pull request Jan 30, 2025
dabla pushed a commit to dabla/airflow that referenced this pull request Jan 30, 2025
ambika-garg pushed a commit to ambika-garg/airflow that referenced this pull request Jan 30, 2025
niklasr22 pushed a commit to niklasr22/airflow that referenced this pull request Feb 8, 2025
ambika-garg pushed a commit to ambika-garg/airflow that referenced this pull request Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:API Airflow's REST/HTTP API legacy api Whether legacy API changes should be allowed in PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants