[v3-0-test] Set proper limits for task-sdk in v3-0-test branch #50164
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
The task SDK we have currently is not yet fully decoupled from the Airflow version we are going to have. It is simply not "future compatible" yet. The "true" decoupling will come when we have Airflow 3.1, for now the task-sdk we have is really tied with 3.1.* version of Airflow - and for now we should have the limits set properly for core: * Lower >= 3.0.0 -> the main version of task-sdk will only work with airflow 3.0.* (including pre-releases) * Upper < 3.1.0 -> the task-sdk from main (1.1.0) will not work with Airflow 3.0.* and it's not going to be installable for Airflow 3.0 as well. Related to apache#50163
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The task SDK we have currently is not yet fully decoupled from the Airflow version we are going to have. It is simply not "future compatible" yet.
The "true" decoupling will come when we have Airflow 3.1, for now the task-sdk we have is really tied with 3.1.* version of Airflow - and for now we should have the limits set properly for core:
Related to #50163
^ 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.