Hello everyone, I just merged a PR where I figured out much nicer (and fully automated) way of maintaining requirements (or rather constraints) for Apache Airflow - we keep the same properties of repeatable installation (with a slightly changed command line for it in the future) but now you should not have to generate requirements when setup.py changes.
We will continue receiving early warnings when transitive dependencies change - but this time it should not even impact regular PRs. Committers will have to deal with it by changing setup.py and it should auto-heal. Details in the CI.rst docs in this PR: https://github.com/apache/airflow/pull/9889 J. -- Jarek Potiuk Polidea | Principal Software Engineer M: +48 660 796 129
