potiuk opened a new pull request #13409: URL: https://github.com/apache/airflow/pull/13409
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. This is a final step of making airflow package fully independent from the provider's dependencies. <!-- Thank you for contributing! Please make sure that your code changes are covered with tests. And in case of new features or big changes remember to adjust the documentation. Feel free to ping committers for the review! In case of existing issue, reference it using one of the following: closes: #ISSUE related: #ISSUE How to write a good git commit message: http://chris.beams.io/posts/git-commit/ --> --- **^ Add meaningful description above** Read the **[Pull Request Guidelines](https://github.com/apache/airflow/blob/master/CONTRIBUTING.rst#pull-request-guidelines)** for more information. In case of fundamental code change, Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)) is needed. In case of a new dependency, check compliance with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x). In case of backwards incompatible changes please leave a note in [UPDATING.md](https://github.com/apache/airflow/blob/master/UPDATING.md). ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
