When we see a providers is a dependency in "cross-provider-dependecies" - we add it automatically - when we build the package - as optional extra. However a number of providers also have the same provider as required dependency, and in this case adding an extra makes little sense.
When we see a providers is a dependency in "cross-provider-dependecies" - we add it automatically - when we build the package - as optional extra. However a number of providers also have the same provider as required dependency, and in this case adding an extra makes little sense.
Example https://airflow.apache.org/docs/apache-airflow-providers-jdbc/stable/index.html#cross-provider-package-dependencies - JDBC provider has "common.sql" extra but it also have "common.sql" as required dependency.
If that is the case, we should skip generating extra when the provider is prepared. This happens in https://github.com/apache/airflow/blob/81a910db9af72db0c7d12c33bb186cb8b117322e/dev/breeze/src/airflow_breeze/utils/packages.py#L471