Skip to content
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

Support upper bound in provider dependencies #40465

Conversation

jscheffl
Copy link
Contributor

Following the discussions in https://apache-airflow.slack.com/archives/C06K9Q5G2UA/p1719428745370839 this PR provides a fix for breeze and version handling logic if an upper limit version is defined.

Foud in AIP-69 PoC PR in https://github.com/apache/airflow/actions/runs/9668809749/job/26674145127?pr=40224 as the new provider remote attempted to define the dependency to airflow as apache-airflow>=2.10.0,<3.0 as it will require Airflow 2.10 and it is assumed due to planned breaking changes it will not work with Airflow 3.0 anymore.

Note: Thought about a pytest but existing pytest depends on providers and did not want to make an artificial provider upper limit. Would offer to make a test in PR #40224

related: #40224

@jscheffl jscheffl force-pushed the bugfix/handle-airflow-packe-dependency-upper-limit branch from 99ec716 to a9a1c08 Compare June 27, 2024 21:03
@jscheffl jscheffl merged commit 271bfa6 into apache:main Jun 28, 2024
80 checks passed
jscheffl added a commit to jscheffl/airflow that referenced this pull request Jun 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants