f49f36b6a0
This change removes the provider-imposed requirements from the airflow's setup.cfg to additional configuration in the breeze/CI scripts. This does not change constraint apprach when installing airflow, the constraints to those versions remain as they were, but airflow package does not have to have the limits in 'install_requires' section which makes it much more "standalone. We can add more requirements there as needed or remove them when provider's dependencies change. Also thanks to using --upgrade-to-newer-dependencies flag in Breeze, the instructions on what to do when there is a problem with conflicting dependencies are much simpler. You do not need any more to set the label in PR to test how upgrade to newer dependencies will look like, you can test it yourself locally. This is a final step of making airflow package fully independent from the provider's dependencies. |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| workflows | ||
| PULL_REQUEST_TEMPLATE.md | ||
| SECURITY.rst | ||
| boring-cyborg.yml | ||
| mergeable.yml | ||
| stale.yml | ||