-
Notifications
You must be signed in to change notification settings - Fork 16.1k
Change v1 to v2 in generated OpenAPI schema files #50705
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jedcunningham
approved these changes
May 16, 2025
bugraoz93
approved these changes
May 16, 2025
Contributor
bugraoz93
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, Kaxil! Make sense!
vincbeck
approved these changes
May 16, 2025
3dd8d44 to
ff54906
Compare
To remove confusion with APIv1, let's align filesnames too.
Member
|
Question @kaxil -> is this one airflow 3.1 or Airflow 3.0.* cherry-pickable ? |
Member
Author
|
cherry-pickale but have to deal with some conflicts so didn't do. No user impact so can go in 3.1 too |
Member
9 tasks
sanederchik
pushed a commit
to sanederchik/airflow
that referenced
this pull request
Jun 7, 2025
kaxil
added a commit
that referenced
this pull request
Jun 10, 2025
(cherry picked from commit baf5fae)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area:airflow-ctl
area:API
Airflow's REST/HTTP API
area:dev-tools
area:providers
area:UI
Related to UI/UX. For Frontend Developers.
kind:documentation
provider:fab
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
(depends on #50704)
To remove confusion with APIv1, let's align filesnames too.
^ 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.rstor{issue_number}.significant.rst, in airflow-core/newsfragments.