I assume this is not necessary when the constraint is already set on the provider side? For example, FAB provider has a dependency on Airflow 3 (`apache-airflow>=3.0.0` in `providers/fab/pyproject.toml`)
On 2025/04/10 17:22:13 Jarek Potiuk wrote: > Hello, > > TL;DR; Do people who work on some providers think that Airflow 3 should > have minimum version of those? > > While discussing a question about chicken-egg providers with Kaxil, I > realized that we can finally have min versions of providers easily added to > "apache-airflow" meta-package. > > Simply speaking - we can say that for example > > apache-airflow[openlineage] -> apache-airflow-providers-openlineage>=2.1.3 > > Previously it was not that easy or straightforward, but now we can do it > easily - just changing: > > "openlineage" = [ > "apache-airflow-providers-openlineage" > ] > into > > "openlineage" = [ > "apache-airflow-providers-openlineage>=2.1.3" > ] > > We will likely have to change the tooling a bit to adapt to RC / Dev > packaging versions for chicken-egg-providers - but this should be rather > easy. > > And I think this is mostly about openlineage, standard, common and all the > other kinds of providers that are "special" in some ways. > > Are we aware of some minimum versions we **SHOULD** put on those ? > > J. > > > > So the question is. > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org For additional commands, e-mail: dev-h...@airflow.apache.org
